Multi-domain intent handling with cross-domain contextual signals

ABSTRACT

A multi-tier domain is provided for processing user voice queries and making routing decisions for generating responses, including for user voice queries that include multi-domain trigger words or phrases. When an utterance is recognized as different intents in different domains, a routing system for a domain may consider contextual signals, including those associated with other domains, to determine whether the domain is the proper one to handle the request. This determination can be performed with a statistical model specifically trained to make such determinations using the available contextual data.

CROSS-REFERENCE TO CONCURRENTLY-FILED APPLICATIONS

This application is being filed concurrently with the following U.S. applications, each of which is incorporated herein by reference in its entirety.

U.S. application Ser. No. Attorney Docket Title Filing Date TBD SEAZN.1832A MULTI-TIER SPEECH PROCESSING AND Jun. 24, 2021 CONTENT OPERATIONS TBD SEAZN.1834A PRIORITY AND CONTEXT-BASED ROUTING Jun. 24, 2021 OF SPEECH PROCESSING TBD SEAZN.1835A DYNAMIC CONTEXT-BASED ROUTING OF Jun. 24, 2021 SPEECH PROCESSING TBD SEAZN.1836A EARLY INVOCATION FOR CONTEXTUAL DATA Jun. 24, 2021 PROCESSING

BACKGROUND

Electronic devices, such as voice-enabled electronic devices, are capable of performing various functions. For instance, an individual may speak a command to activate such a device, and in response the device may perform various functions and/or cause one or more actions to be performed. Some voice-enabled electronic devices may communicate with a network-accessible system for processing of spoken commands, performance of functions, and the like.

BRIEF DESCRIPTION OF DRAWINGS

Embodiments of various inventive features will now be described with reference to the following drawings. Throughout the drawings, reference numbers may be re-used to indicate correspondence between referenced elements. The drawings are provided to illustrate example embodiments described herein and are not intended to limit the scope of the disclosure.

FIG. 1 is a block diagram showing data flows an interactions between systems and components of an illustrative networked speech processing environment according to some embodiments.

FIG. 2 is a diagram of an illustrative architecture of systems shown of FIG. 1 according to some embodiments.

FIG. 3 is a diagram of illustrative data flows and interactions between components of an intra-domain routing system and other components of a speech processing system according to some embodiments.

FIG. 4 is a flow diagram of an illustrative process for intra-domain routing using contextual data according to some embodiments.

FIG. 5 is a diagram of an illustrative multi-tier domain configuration according to some embodiments.

FIG. 6 is a diagram of illustrative data flows and interactions between a contextual data management system and other components of a speech processing system according to some embodiments.

FIG. 7 is a flow diagram of an illustrative process for managing contextual data according to some embodiments.

FIG. 8 is a diagram of illustrative data flows and interactions between components of a contextual data management system and other components of a speech processing system according to some embodiments.

FIG. 9 is a diagram of an illustrative multi-tier, multi-domain configuration according to some embodiments.

FIG. 10 is a diagram of an illustrative model configured to evaluate contextual data and generate routing evaluation output according to some embodiments.

FIG. 11 is a flow diagram of an illustrative process for managing routing among intent processing applications according to some embodiments.

FIG. 12 is a diagram of illustrative data flows and interactions of an intra-domain routing system to generate a routing evaluation for an utterance with a multi-domain trigger according to some embodiments.

FIG. 13 is a diagram of illustrative data flows and interactions of an intra-domain routing system to generate a routing evaluation for an utterance with a multi-domain trigger according to some embodiments.

DETAILED DESCRIPTION

The present disclosure is directed to a system that uses contextual data to determine the specific domains, subdomains, and intent processing applications appropriate for taking action in response to spoken commands and other utterances. In some embodiments, the system can use signals and other contextual data associated with an utterance, such as location signals, content catalog data, data regarding historical usage patterns, data regarding content visually presented on a display screen of a computing device when an utterance was made, other data, or some combination thereof. By incorporating contextual data into the routing decisions for responding to—or otherwise taking action on—potentially ambiguous spoken utterances, a speech processing system can provide an improved user experience in terms of user-perceived latency and success in accomplishing the users' interaction goals.

Some speech processing systems process utterances by generating transcripts or other textual representations of the utterances using automatic speech recognition (“ASR”), and then analyzing the textual representations to determine their meaning using natural language understanding (“NLU”). The systems then perform one or more actions based on the determined meanings of the utterances. However, some utterances may be ambiguous and may reasonably be interpreted as requests for performance of any number of different actions, and some actions may be appropriately performed in any number of different manners and/or by any number of applications. Some speech processing systems attempt to account for such ambiguity through the use of contextual data to aid in determining the meaning of an utterance. The utterance may then be routed to an application for performance of an action associated with the determined meaning. However, such systems may not have access to all relevant contextual data at the time the initial utterance meaning is determined or may not otherwise be capable of considering all relevant contextual data during utterance meaning determination. For these reasons, among others, the systems may not accurately determine the most appropriate actions to be performed or otherwise most appropriate applications for performance of the actions. Moreover, new actions and applications cannot be integrated into the system, and new contextual data cannot be accounted for and considered, without changes to the underlying NLU processing.

Some aspects of the present disclosure address the issues noted above, among others, by providing context-aware routing of utterances to particular domains and domain-specific applications for processing. In some embodiments, a speech processing system implements utterance processing using a set of domains. Generally described, a domain is a collection of applications (also referred to as “experience provider services,” “experience providers,” or “services”) each configured to respond to utterances associated with a particular utterance subject matter, such as a particular subset of voice commands and other intents the speech processing system is capable of understanding. A response to an utterance may include automatically executing a function, engaging in a multi-turn spoken dialog, other actions, or some combination thereof. For example, one domain may be a shopping domain configured to process all manner of shopping related commands and queries. Another domain may be a media content management service on which a user accesses media content that they own, license, or access third party media. Yet another domain may be a communication domain configured to initiate phone calls and generate emails, etc. The specific actions that are performed by the domains in response to utterances may be handled by specialized applications implemented as combinations of software and hardware. Segregating the functionality of the speech processing system into domains can allow for easier addition and modification of the universe of commands and queries that the speech processing system is capable of accepting. However, in such a configuration, routing utterances to the proper domain—or to the proper application within a given domain—becomes an important task because applications of one domain may be unable to adequately process utterances associated with the subject matter of another domain. In addition, some domains may be large and may be organized into subdomains in any number of tiers. In such cases, routing an utterance to the proper subdomain may present additional complexity.

To improve the routing of utterances to particular domains, subdomains, and applications, an intra-domain routing system may employ any number of subdomain-specific and/or application-specific confidence providers to obtain assessments of which subdomains and/or applications (if any) are appropriate destinations for a particular utterance. For example, an ASR system may generate text data representing a transcript or set of words in an utterance, and an NLU system can then generate an N-best list (where N is a positive integer) of interpretations of the utterance that the speech processing system is configured to process. The interpretations of the utterance may also be referred to as “intents.” The domains associated with one or more of the N-best intents may be identified and requested to indicate whether they are capable of adequately handling the intent(s). Within a particular domain, the subdomain and/or application specific confidence providers associated with the intent(s) may be requested to provide an assessment of the likelihood that the corresponding subdomains and/or applications are the proper entity for responding to the utterance.

The assessments of the confidence providers may be based not only on the utterance itself (e.g., the NLU-generated intent, ASR-generated text data, etc.), but also on contextual data associated with the utterance. For example, a domain may be a shopping domain configured to process all manner of shopping related commands and queries. The shopping domain may have any number of intent processing applications, which may or may not be separated into any number of subdomains, including a first subdomain associated with finding products in a particular store and a second subdomain associated with purchasing products online. When a user says “find me product X,” the proper entity for handling this utterance may depend on contextual data associated with the utterance, such as the user's geographic location: if the user is at the particular store, then the proper entity may be the first subdomain and/or application, while if the user is at home, then the proper entity may be the second subdomain and/or application. The confidence providers can be provided with contextual data indicating the user's geographic location, and the confidence providers may produce different assessments for different users and/or different utterances depending upon the user's geographic location at the time of the utterance. Advantageously, consideration of contextual information during the routing confidence evaluations is separate from consideration of contextual information (if any) during NLU intent determinations, and may include additional contextual information and/or altogether different contextual information.

Additional aspects of the present disclosure relate to proactively obtaining and managing contextual information during utterance processing for use in subsequent routing determinations, response generation operations, and other downstream processes. A contextual data management system may be integrated at various points into the process of receiving and processing an utterance to generate intents. As data is generated, accessed, or otherwise becomes available during utterance processing, the contextual data management system can identify and obtain the contextual data that is to be used in routing confidence evaluations. The obtained contextual data can be stored, processed, used to generate and/or obtain additional contextual data, etc. In some embodiments, the contextual data management system may maintain a registry of contextual data items to be obtained, the points of integration at which the contextual data items are to be obtained, the processing/storage/etc. to be performed using the contextual data, which routing confidence evaluations use the contextual data items, etc. For example, the registry may indicate that one contextual data item may become available at a particular point during utterance processing, and is to be used as input into a calculation or evaluated by a model to produce a particular value that is to be considered during a routing confidence evaluation. As another example, the registry may indicate that another contextual data item may become available at another point during utterance processing, and is to be stored for consideration during another routing confidence evaluation. The registry may define any number and combination of such contextual data item acquisition processes, and the contextual data management system may use the registry to acquire the contextual data items and make them available for routing confidence evaluations. In some embodiments, the registry may associate contextual data items with particular confidence providers.

Further aspects of the present disclosure relate to evaluating utterances that have a comparatively high likelihood of being interpreted as any of multiple different intents in multiple different domains. Some utterances, such as those involving requests to “show” the user something, may be interpreted in two or more different domains of a multi-domain architecture. Illustratively, a multi-domain architecture may include a shopping domain for browsing and acquiring products, and a smart home domain for managing smart home devices. The utterance “Show security cameras” may be interpreted as a request to browse for security cameras to be acquired, or as a request to show the current video stream generated from smart home security cameras that have already been acquired and are in use in the user's home. The correct interpretation depends on context surrounding the utterance, such as whether the user is shopping for other things when the “Show security cameras” utterance is made, whether the user has previously acquired and set up home security cameras for use, etc. Utterances that may reasonably be interpreted in multiple domains may give rise to an unacceptably high number of false acceptances and/or false rejections if the contextual data relevant to disambiguating the utterances in each instance is not considered in the routing evaluations that are made within each domain. For example, an intra-domain routing system for the shopping domain may determine with a high degree of confidence that the utterance “Show security cameras,” as represented by a “shopping-search-item” intent, is properly handled by a shopping-related search and display application, while an intra-domain routing system for the smart home domain also determines with a high degree of confidence that the same utterance, as represented by a “smart-home-display-video” intent, is properly handled by a home video camera display application. Without the proper contextual signals, including signals associated with other domains, the routing evaluations made by the intra-domain routing systems may cause false routing determinations to be made. To address this issue, an intra-domain routing system, upon receiving a fulfillment request, may make an initial determination as to whether the request relates to an utterance with a multi-domain trigger word or phrase. If so, a routing evaluation may be made using a set of deterministic rules or a statistical model specifically designed to evaluate such requests with additional contextual information, in some cases including contextual information associated with other domains. In this way, the incidence of false acceptances for utterances with multi-domain triggers can be reduced.

Various aspects of the disclosure will now be described with regard to certain examples and embodiments, which are intended to illustrate but not limit the disclosure. Although aspects of some embodiments described in the disclosure will focus, for the purpose of illustration, on particular examples of utterances, intents, applications, routing determinations and contextual data items, the examples are illustrative only and are not intended to be limiting. In some embodiments, the techniques described herein may be applied to additional or alternative utterances, intents, applications, routing determinations and contextual data items, and the like.

Speech Processing Environment

FIG. 1 is a schematic diagram of an illustrative network environment in which a user 104 makes an utterance 106, one or more voice-enabled devices 102 detect the utterance 106, and a speech processing system 100 determines the meaning of—and performs an action in response to—the utterance 106.

In some embodiments, the voice-enabled device 102 may have one or more microphones that are used to capture user speech, such as the utterance 106, one or more speakers that are used to play speech (e.g., computer-synthesized dialogue) or other content, one or more displays that are used to present content, etc. The voice-enabled device 102 may also be referred to as a user computing device or a user device. In some embodiments, the voice-enabled device 102 may be portable or mobile. For example, the voice-enabled device 102 may be a handheld device or other mobile device such as a mobile phone or tablet computer. In some embodiments, the voice-enabled device 102 may be designed to operate from a relatively fixed location. For example, the voice-enabled device may be a speaker configured with audio input capabilities and network access (e.g., a “smart speaker”), a screen configured with audio input capabilities and network access (e.g., a “smart display”), or some other electronic device.

The speech processing system 100 may process audio signals received from the voice-enabled device 102 and formulate responses to the user 104. The speech processing system 100 may include various components for providing the features described herein. In some embodiments, the speech processing system 100 may include an ASR system 202 to process audio signals or other audio data and generate text data representative of user utterances. The speech processing system 100 may also include an NLU system 204 to process text data and generate semantic representations of user utterances. The speech processing system 100 may also include a system of domains 206 that each include or manage one or more applications 282 to respond or otherwise act on user utterances, such as by providing requested content, performing requested operations, and the like. Advantageously, individual domains 206 (or certain subsets thereof) may be associated with a corresponding intra-domain routing system 212 to determine whether particular utterance meaning hypotheses, generated by the NLU system 204, are able to be handled by applications 282 of the corresponding domain 206. The speech processing system 100 may also include a contextual data management system 214 to manage the acquisition, generation, and provision of contextual data to the intra-domain routing system(s) 212 for use in making routing determinations, generating responses, etc. The determinations made by the intra-domain routing systems 212 may be used by a inter-domain routing system 210 to manage the routing of utterances to individual domains 206 or applications 282.

The example systems and components of the speech processing system 100 shown in FIG. 1 are illustrative only, and are not intended to be limiting. In some embodiments, a speech processing system 100 may have fewer, additional, and/or alternative components and data stores. A specific, detailed example embodiment of the speech processing system 100 is shown in FIG. 2 and described in greater detail below.

The speech processing system 100 may be implemented on one or more physical server computing devices that provide computing services and resources to end-user devices, such as voice-enabled devices 102. In some embodiments, the speech processing system 100 (or individual components thereof, such as the ASR system 202, NLU system 204, domain systems 206, inter-domain routing system 210, intra-domain routing systems 212, contextual data management system 214, etc.) may be implemented on one or more host devices, such as blade servers, midrange computing devices, mainframe computers, desktop computers, or any other computing device configured to provide computing services and resources. For example, a single host device may execute one or more ASR systems 202, NLU systems 204, domain systems 206, inter-domain routing system 210, intra-domain routing systems 212, contextual data management system 214, some combination thereof, etc. The speech processing system 100 may include any number of such hosts.

In some embodiments, the features and services provided by the speech processing system 100 may be implemented as web services consumable via one or more communication networks. In further embodiments, the speech processing system 100 (or individual components thereof) is provided by one more virtual machines implemented in a hosted computing environment. The hosted computing environment may include one or more rapidly provisioned and released computing resources, such as computing devices, networking devices, and/or storage devices. A hosted computing environment may also be referred to as a “cloud” computing environment.

As shown in FIG. 1 , a user 104 may interact with a voice-enabled device 102 using an utterance 106. The voice-enabled device 102 may detect sound corresponding to the utterance 106 of the user via one or more microphones. In certain implementations, the utterance 106 may include or be preceded by a wakeword or other trigger expression or event (e.g., “Computer!”) that is spoken by the user 104 to indicate that subsequent user speech (e.g., “Where can I find coffee?”) is device-directed speech (e.g., speech intended to be received and acted upon by the voice-enabled device 102 and/or speech processing system 100). The voice-enabled device 102 may detect the wakeword and begin streaming audio signals to the speech processing system 100. In some instances, the voice-enabled device 102 may operate in a low-functionality mode and analyze sound using ASR processing. When the wakeword is detected (e.g., using ASR, keyword spotting, etc.), the voice-enabled device 102 may begin streaming the audio signal (and, optionally, other data) to the speech processing system 100. The wakeword may be a reserved keyword that is detected locally by the voice-enabled device 102, such as by using an expression detector that analyzes audio signals produced by the microphones of the voice-enabled device 102 to detect the wakeword, which generally may be a predefined word, phrase, or other sound. Such an expression detector may be implemented using keyword spotting technology, as an example.

In the example illustrated in FIG. 1 , the user 104 issues an utterance 106 subsequent to a wakeword, which the voice-enabled device 102 captures. The voice-enabled device 102 may produce an audio signal representing the utterance 106. As shown, the voice-enabled device 102 may send the audio signal to the speech processing system 100. In some embodiments, the voice-enabled device 102 may further determine and/or generate, and send additional metadata to the speech processing system 100 that may be used to determine various terms in the utterance 106. For instance, the types of metadata may include data regarding the information currently displayed on a display component (or some other display), sensor data representing the current location and/or environment of the voice-enabled device 102, snapshots which indicate device states of the voice-enabled device 102, data about the voice-enabled device 102 (e.g., unique identifier, version), etc. Data regarding the information currently displayed may include identifiers of content items currently displayed on screen, identifiers of items displayed in a list, etc. Sensor data may comprise data generated by various sensors and other components of the voice-enabled device, such as data representing geolocation, ambient temperature, ambient lighting, device orientation, device motion, and the like. A snapshot may comprise device states which indicate current operations of the voice-enabled device 102 before, during, and/or after the utterance 106 is detected by the voice-enabled device 102. Device states of the voice-enabled device 102 may represent actions such as, for example, conducting a telephone call, outputting an alarm sound, streaming audio (e.g., music, audio books, etc.), conducting a dialogue with user 104, performing online searches, controlling appliances in a house, or any other type of activity for which a voice-enabled device 102 can be configured to perform. Data about the voice-enabled device 102 may include a device identifier, a version identifier, data regarding components and/or capabilities of the voice-enabled device 102 (e.g., whether the device has a display screen, a touch screen, a speaker, a microphone, a keyboard, etc.), data regarding a network connection available to the voice-enabled device 102, geolocation or local location data regarding the location of the voice-enabled device 102, etc.

While the snapshots of the device states may be sent to the speech processing system 100 when an utterance is detected 106, in other examples, the speech processing system 100 may also store indications of device states rather than receiving them each time an audio signal is received. For example, the speech processing system 100 may receive an indication that the user 104 set an alarm, and know what time the alarm will sound. Thus, once the alarm is sounding, the speech processing system 100 may already have the device state stored and does not receive the snapshots every time an utterance 106 is detected. Similarly, some or all of the metadata may be stored at the speech processing system 100 prior to the utterance 106 being captured by the voice-enabled device 102.

With reference to an illustrative example, the user 104 may make an utterance 106 such as “Where can I find coffee?” At [A], an audio signal representing the user's utterance 106 may be transmitted to the speech processing system 100 for processing and responsive action. Based only on the spoken words, the utterance 106 may be ambiguous: it could be a query for a physical coffee shop nearby; it could be a query for the location of coffee within a physical store; it could be a query for an online purchase of coffee. Each of these interpretations, and potentially others, may be plausible. Conventional systems may rank the possible interpretations, select the top-ranked interpretation, and route the query to an application for performance of an associated action. However, without considering contextual data associated with the utterance, the routing of the query to an application may not be appropriate. For example, if a user is in a store that sells coffee, the second interpretation (it is a query for the location of coffee within a physical store) may be the most likely correct interpretation, while if a user is at home looking at a shopping web site, the third interpretation (it is a query for an online purchase of coffee) may be the most likely correct interpretation. Different applications may be used perform actions in response to these different interpretations. By considering contextual information such as the current location of the user, the user's current activities and/or interactions with the voice-enabled device 102, etc., the system 100 can make dynamic routing determinations that vary from user-to-user, and even from query-to-query even when received from the same user.

At [B], the ASR system 202 can generate ASR results using the audio signal. Illustratively, the ASR results may include one or more transcripts or other sets of text data representative of words in the utterance 106. In some examples, the ASR system 202 may generate ASR confidence score data representing the likelihood that a particular set of words of the textual data matches those spoken in the utterance 106. For instance, the ASR system 202 may determine a score representing a confidence or likelihood that a particular word which matches the sounds would be included in the sentence at the specified location (e.g., using a language or grammar model). Thus, each potential textual interpretation of the spoken utterance 106 (hypothesis) is associated with an ASR confidence score. The ASR system 202 may send the ASR results to the NLU system 204 at [C].

At [D], the NLU system 204 may generate NLU results data, such as a semantic representation of the utterance 106, using the obtained ASR results. In the present example, as described above, the utterance “Where can I find coffee?” may reasonably be interpreted as a query for a location of a physical coffee shop, a query the location of coffee within a physical store, a query for coffee in an online store, etc. The NLU system 204 may generate an N-best list of interpretations, including any or all of these interpretations and potentially others. The NLU system 204 may provide the NLU results to the inter-domain routing system 210 at [E].

At [B′], the contextual data management system 214 may obtain and/or generate contextual data at various integration points throughout the intake, ASR, and NLU processes. The acquisition of contextual data is shown using the label [B′-F′] to indicate the parallel or otherwise asynchronous operation with respect to other processes shown and described, including those labeled [B]-[F]. For example, the contextual data management system 214 may obtain geolocation data representing the current geographic location of the voice-enabled device 102. This data may be obtained by the system 100 with the audio signal at [A] and then provided to the contextual data management system 214, requested by the system 100 after receipt of the audio signal and then provided to the contextual data management system 214, or otherwise obtained by the contextual data management system 214. In some embodiments, the geolocation data may be obtained by the contextual data management system 214 in parallel with ASR processing at [B], provision of ASR results at [C], NLU processing [D], provision of NLU results at [E], or at some other time (e.g., the data may be available from processing a prior utterance). The contextual data management system 214 may obtain and/or generate other contextual data items before, in parallel with, or after ASR processing at [B], provision of ASR results at [C], NLU processing [D], provision of NLU results at [E], and/or at various other times (e.g., during processing of a prior utterance). For example, the contextual data management system 214 may obtain data regarding content being presented by the voice-enabled device 102 when the utterance 106 was made (e.g., web pages, list items, etc.), partial or complete ASR results, partial or complete NLU results, etc. As another example, the contextual data management system 214 may perform operations based on the ASR and/or NLU results, such as determining a difference in scoring between top-ranked NLU results, performing initial classification of the utterance 106 as being related or unrelated to a prior interaction with the system 100, generating encodings of portions of partial NLU results, etc. These contextual data items may be stored or otherwise made accessible to routing confidence providers for use in routing determinations and/or generating a response to the utterance.

At [F], the inter-domain routing system 210 can determine the domain(s) from which to generate a request for evaluation of routing confidence (e.g., a request for a determination regarding whether the domain or an application thereof is the proper entity to respond to the utterance). This request may be referred to as a “confidence request” or a “fulfillment request.”

In some embodiments, the inter-domain routing system 210 may maintain or otherwise have access to a mapping of which domain(s) are configured to handle or are otherwise associated with which intent(s) that the NLU system 204 is configured to generate. The inter-domain routing system 210 may receive a list of one or more intents from the NLU system 204 for the current utterance 106, such as an N-best list. The inter-domain routing system 210 may iterate through the N-best list, or a portion thereof, and use the mapping to identify the domain(s) associated with the intent(s). The inter-domain routing system 210 may then generate a confidence request for each identified domain, and send the request to the intra-domain routing system 212 associated with each identified domain. A confidence request may include intent data representing one or more intents mapped to the domain to which the request is sent. The request may include additional information, such as score or ranking data indicating the relative likelihood that the intent is the proper intent as judged by the NLU system 204.

In the present example, an N-best list of three intents may be provided to an intra-domain routing system 212 for a shopping domain: one intent that corresponds to a query for a location of a physical coffee shop, one intent that corresponds to a query for the location of coffee within a physical store, and one intent that corresponds to a query for coffee in an online store. Additional intents may be provided to one or more other intra-domain routing systems 212 for other domains. For example, the N-best list of intents that is received by the inter-domain routing system 210 at [E] may include the three intents for the shopping domain described above, an intent for a hospitality domain (e.g., to find out if there is coffee in a hotel room), an intent for a video content domain (e.g., to find a video with the word “coffee” in the title). The inter-domain routing system 210 can generate confidence requests for those other two domains in addition to the confidence request generated for the shopping domain. In some embodiments, the confidence requests sent to the intra-domain routing systems 212 for the different domains may be made and/or handled serially, or in some embodiments the requests may be made and/or handled in parallel or otherwise asynchronously.

At [G], the intra-domain routing system 212 in receipt of each confidence request can obtain contextual data for use in routing confidence evaluations. Contextual data may include, but is not limited to: data regarding prior utterances of the current session, data regarding utterances of prior sessions, data regarding items presented on a screen when the current utterance was made, data regarding the domain(s) associated with the items presented on a screen when the current utterance was made, data regarding entities recognized during NLU processing, data regarding entities resolved during NLU processing, data regarding user feedback during the current or prior session, data regarding the purchase history of the user, data regarding the interaction history of the user, data regarding specified or learned user preferences, data regarding user accessibility history and/or preferences, geolocation data, data regarding device capabilities, data regarding device properties, data regarding user digital content library items, data regarding user subscriptions, data regarding user purchase history, gazetteer data regarding presence and/or absence of domain terms, other data, or some combination thereof. The example contextual data items described herein are illustrative only, and are not intended to be limiting, required, or exhaustive.

In the present example, the intra-domain routing system 212 for the shopping domain may obtain location data representing the geographic location of the voice-enabled device 102. As another example, the intra-domain routing system 212 for the shopping domain may obtain data representing content displayed on a screen of the voice-enabled device 102 when the utterance 106 was made.

At [H], the intra-domain routing system 212 in receipt of each confidence request can generate one or more routing confidence evaluations. In some embodiments, an intra-domain routing system 212 may employ any number of application-specific confidence providers to obtain assessments of which subdomains (e.g., applications) are appropriate destinations for a particular utterance. For example, the intra-domain routing system 212 for the shopping domain may request routing confidence evaluations from each of three application-specific routing confidence providers: a first routing confidence provider for the physical store locator application, a second confidence provider for an in-store product locator application, and a third routing confidence provider for an online shopping application. Requests for routing confidence evaluations may be made and/or handled serially, or in some embodiments the requests may be made and/or handled in parallel or otherwise asynchronously. In some embodiments, requests for routing confidence evaluations may include the various contextual data items, if any, used by the respective application-specific routing confidence providers. For example, the routing confidence provider for the physical store locator and the in-store product locator application may receive contextual data representing the geographic location of the voice-enabled device 102, while the routing confidence provider for the online shopping application may receive contextual data representing the geographic location and also the content (if any) displayed by the voice-enabled device 102 when the utterance 106 occurred.

In some embodiments, a routing confidence evaluation may be a confidence score representing the confidence of the respective provider that the application associated with provider is the proper application to handle the intent. The score may be determined using deterministic rules, a statistical model, or a combination thereof. The routing confidence evaluations may be provided to the inter-domain routing system 210 at [M].

In the present example, the routing confidence provider for the in-store aisle location application may apply a set of deterministic rules and/or a statistical model to the associated intent (e.g., a “get-aisle-location” intent) and contextual data (e.g., geographic data indicating that the user is in a particular store that offers voice-enabled product location). This routing confidence provider may generate a confidence score that is relatively high, indicating a high confidence that an in-store aisle location application is the proper application to handle the intent. The routing confidence provider for the physical store locator application may apply a set of deterministic rules and/or a statistical model to the associated intent (e.g., an on-the-go store location intent) and contextual data (e.g., geographic data indicating that the user is in the particular store noted above). This routing confidence provider may generate a confidence score that is relatively moderate, indicating a moderate confidence that a physical store locator application is the proper application to handle the intent. The routing confidence provider for the online shopping application may apply a set of deterministic rules and/or a statistical model to the associated intent (e.g., an “browse-online-item” or “purchase-item” intent) and contextual data (e.g., geographic data indicating that the user is in the particular store noted above, and content other than an online shopping site or application is displayed by the voice-enabled device 102 when the utterance 106 occurred). This routing confidence provider may generate a confidence score that is relatively low, indicating a low confidence that an online shopping application is the proper application to handle the intent.

In some embodiments, the intra-domain routing system 212 may compare or otherwise analyze the various routing confidence evaluations (e.g., confidence scores) generated by the routing confidence providers. Based on the analysis, the intra-domain routing system 212 can determine which application of the domain, if any, is likely the best application to handle the intent. In the present example, the intra-domain routing system 212 may determine that the in-store aisle location application is the best application of the shopping domain to handle the intent.

At [J], the inter-domain routing system 210 can determine a domain, subdomain, and/or application assignment based on the routing confidence evaluations received from one or more intra-domain routing systems 212. In the present example, the spoken query of “Where can I find coffee?” may be routed to the in-store aisle location application based on the relatively high confidence score associated with that application in comparison with the other confidence scores for other applications.

At [K], the assigned application 282 may generate a response to the utterance 106. The response may include: executing a function, generating a synthesized spoken response, generating a visual response, performance of some other action, or any combination thereof. For example, executing a function may include initiating a purchase transaction. Generating a synthesized response may include providing requested information in audio form. Generating a visual response may include displaying requested information on a visual display. In the present example, the response may be a synthesized spoken response (e.g., “Coffee is in aisle 20”), a visual response (e.g., a map of the store with the location of the coffee highlighted), or a combination thereof.

At [L], the speech processing system 100 can transmit the generated response, if any, to the voice-enabled device 102, and the voice-enabled device may present the response as needed.

Turning now to FIG. 2 , various examples of components of an embodiment of the voice-enabled device 102 and an embodiment of the speech processing system 100 architecture of FIG. 1 will be described.

A voice-enabled device 102 may correspond to any suitable type of electronic device including, but are not limited to, desktop computers, mobile computers (e.g., laptops, ultrabooks), mobile phones, smart phones, tablets, televisions, set-top boxes, smart televisions, personal display devices, large scale display devices (e.g., billboards, street signs, etc.), personal digital assistants (“PDAs”), gaming consoles and/or devices, smart furniture, smart household devices (e.g., refrigerators, microwaves, etc.), smart vehicles (e.g., cars, trucks, motorcycles, etc.), smart transportation devices (e.g., boats, ships, trains, airplanes, etc.), wearable devices (e.g., watches, pins/broaches, headphones, eyewear, headsets, etc.), and/or smart accessories (e.g., light bulbs, light switches, electrical switches, etc.). In some embodiments, a voice-enabled device 102 may be relatively simple or basic in structure such that no, or a minimal number of, mechanical input option(s) (e.g., keyboard, mouse, track pad) or touch input(s) (e.g., touch screen, buttons) are included. For example, a voice-enabled device 102 may be able to receive and output audio, and may include power, processing capabilities, storage/memory capabilities, and communication capabilities. However, in other embodiments, a voice-enabled device 102 may include one or more components for receiving mechanical inputs or touch inputs, such as a touch screen and/or one or more buttons.

A voice-enabled device 102, in one embodiment, may include a minimal number of input mechanisms (e.g., a power on/off switch) such that functionality of a voice-enabled device 102 may solely or primarily be through audio input and audio output. For example, a voice-enabled device 102 may include, or be in communication with, one or more microphones that listen for a wakeword by continually monitoring local audio. In response to the wakeword being detected, a voice-enabled device 102 may establish a connection with speech processing system 100, send audio data to speech processing system 100, and await/receive a response from speech processing system 100. In some embodiments, however, non-voice/sound enabled devices may also communicate with speech processing system 100. For example, in response to a button or touch screen being pressed, or a button or touch screen being pressed and held, a microphone associated with a voice-enabled device 102 may begin recording local audio, establish a connection with speech processing system 100, send audio data representing the captured audio to speech processing system 100, and await/receive a response, and/or action to be occur, from speech processing system 100.

The voice-enabled device 102 may include one or more processors 220, storage/memory 222, communications circuitry 224, one or more microphones 226 or other audio input devices (e.g., transducers), one or more speakers 228 or other audio output devices, one or more cameras 230 or other image capturing components, and a display component 232. However, one or more additional components may be included within a voice-enabled device 102, and/or one or more components may be omitted. For example, a voice-enabled device 102 may also include a power supply or a bus connector. As still yet another example, a voice-enabled device 102 may include one or more additional input and/or output mechanisms, such as one or more sensors, one or more buttons, or one or more switches or knobs. Furthermore, while a voice-enabled device 102 may include multiple instances of one or more components, for simplicity only one of each component has been shown.

In some embodiments, a voice-enabled device 102 may correspond to a manually activated device, or may include the functionality of a manually activated device. A manually activated device, as described herein, may correspond to a device that is capable of being activated in response to a manual input (e.g., pressing a button, touching a portion of a touch screen, performing an action on a device). For example, a tap-to-talk device is one type of manually activated device. Such tap-to-talk devices, for instance, are capable of obtaining and outputting audio data in response to a button being pressed.

Processor(s) 220 may include any suitable processing circuitry capable of controlling operations and functionality of a voice-enabled device 102, as well as facilitating communications between various components within a voice-enabled device 102. In some embodiments, processor(s) 220 may include a central processing unit (“CPU”), a graphic processing unit (“GPU”), one or more microprocessors, a digital signal processor, or any other type of processor, or any combination thereof. In some embodiments, the functionality of processor(s) 202 may be performed by one or more hardware logic components including, but not limited to, field-programmable gate arrays (“FPGA”), application specific integrated circuits (“ASICs”), application-specific standard products (“ASSPs”), system-on-chip systems (“SOCs”), and/or complex programmable logic devices (“CPLDs”). Furthermore, each of processor(s) 220 may include its own local memory, which may store program systems, program data, and/or one or more operating systems. However, processor(s) 220 may run an operating system (“OS”) for a voice-enabled device 102, and/or one or more firmware applications, media applications, and/or applications resident thereon. In some embodiments, processor(s) 220 may run a local client script for reading and rendering content received from one or more websites. For example, processor(s) 220 may run a local JavaScript client for rendering HTML or XHTML content received from a particular URL accessed by a voice-enabled device 102.

Storage/memory 222 may include one or more types of storage mediums such as any volatile or non-volatile memory, or any removable or non-removable memory implemented in any suitable manner to store data for a voice-enabled device 102. For example, data may be stored using computer-readable instructions, data structures, and/or program systems. Various types of storage/memory may include, but are not limited to, hard drives, solid state drives, flash memory, permanent memory (e.g., ROM), electronically erasable programmable read-only memory (“EEPROM”), CD-ROM, digital versatile disk (“DVD”) or other optical storage medium, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage systems, or any other storage type, or any combination thereof. Furthermore, storage/memory 222 may be implemented as computer-readable storage media (“CRSM”), which may be any available physical media accessible by processor(s) 220 to execute one or more instructions stored within storage/memory 222. In some embodiments, one or more applications (e.g., gaming, music, video, calendars, lists, etc.) may be run by processor(s) 220, and may be stored in memory 222.

In some embodiments, storage/memory 222 may store voice biometric data associated with one or more individuals. For example, an individual that operates a voice-enabled device 102 may have a registered user account or other profile data on speech processing system 100 (e.g., within a user data store 216). In some embodiments, a voice-enabled device 102 may be associated with a group account, and various individuals may have user accounts that are operating under the rules and configurations of the group account. As an illustrative example, a voice-enabled device 102 may be associated with a first group account on the speech processing system 100, the first group account being for a family that lives at a household where a voice-enabled device 102 is located. Each family member may also have a user account that is linked to the first group account (e.g., a parent, a child, etc.), and therefore each user account may obtain some or all of the rights of the first group account. For example, a voice-enabled device 102 may have a first group account on speech processing system 100 registered to a particular family or group, and each of the parents and children of the family may have their own user account registered under the parent's registered account. In one illustrative embodiment, voice biometric data for each individual may be stored by that individual's corresponding user account. The voice biometric data, for instance, may correspond to a “voice print” or “voice model” of a particular individual, which may be a graphical representation of a person's voice including a frequency decomposition of that individual's voice.

Communications circuitry 224 may include any circuitry allowing or enabling one or more components of a voice-enabled device 102 to communicate with one another, and/or with one or more additional devices, servers, and/or systems. For example, communications circuitry 224 may facilitate communications between a voice-enabled device 102 and speech processing system 100. As an illustrative example, audio data representing an utterance (e.g., utterance 106 of FIG. 1 ) may be transmitted over a network 150, such as the Internet, to speech processing system 100 using any number of communications protocols, such as Transfer Control Protocol and Internet Protocol (“TCP/IP”) (e.g., any of the protocols used in each of the TCP/IP layers), Hypertext Transfer Protocol (“HTTP”), WebRTC, SIP, wireless application protocol (“WAP”), etc. Communications circuitry 224 may use any communications protocol, such as any of the previously mentioned exemplary communications protocols. In some embodiments, a voice-enabled device 102 may include one or more antennas to facilitate wireless communications with a network using various wireless technologies (e.g., Wi-Fi, Bluetooth, radiofrequency, etc.). In yet another embodiment, a voice-enabled device 102 may include one or more universal serial bus (“USB”) ports, one or more Ethernet or broadband ports, and/or any other type of hardwire access port so that communications circuitry 224 allows a voice-enabled device 102 to communicate with one or more communications networks.

A voice-enabled device 102 may also include one or more microphones 226 and/or transducers. In addition, or alternatively, one or more microphones located within a separate device may be in communication with a voice-enabled device 102 to capture sounds for a voice-enabled device 102. Microphone(s) 226 may be any suitable component capable of detecting audio signals. For example, microphone(s) 226 may include one or more sensors for generating electrical signals and circuitry capable of processing the generated electrical signals. In some embodiments, microphone(s) 226 may include multiple microphones capable of detecting various frequency levels. As an illustrative example, a voice-enabled device 102 may include multiple microphones (e.g., four, seven, ten, etc.) placed at various positions about a voice-enabled device 102 to monitor/capture any audio outputted in the environment where a voice-enabled device 102 is located. The various microphones 226 may include some microphones optimized for distant sounds, while some microphones may be optimized for sounds occurring within a close range of a voice-enabled device 102. In some embodiments, microphone(s) 226 may only begin to detect audio signals in response to a manual input to a voice-enabled device 102. For example, a manually activated device may begin to capture audio data using microphone(s) 226 in response to a user input, such as pressing a button, tapping a touch screen, or providing any touch input gesture to a touch input component.

A voice-enabled device 102 may include one or more speakers 228. Furthermore, a voice-enabled device 102 may be in communication with one or more speaker(s) 228. Speaker(s) 228 may correspond to any suitable mechanism for outputting audio signals. For example, speaker(s) 228 may include one or more speaker units, speaker housings, transducers, arrays of speakers, and/or arrays of transducers that may be capable of broadcasting audio signals and or audio content to a surrounding area where a voice-enabled device 102 may be located. In some embodiments, speaker(s) 228 may include headphones or ear buds, which may be wirelessly wired, or hard-wired, to a voice-enabled device 102, that may be capable of broadcasting audio directly to an individual.

In some embodiments, one or more microphones 226 may serve as input devices to receive audio inputs. A voice-enabled device 102, in the previously mentioned embodiment, may then also include one or more speakers 228 to output audible responses. In this manner, a voice-enabled device 102 may function solely through speech or audio, without the use or need for any input mechanisms or displays, however this is merely exemplary.

Display component 232 may correspond to a display device and/or touch screen, which may be any size and/or shape and may be located at any portion of a voice-enabled device 102. Various types of displays may include, but are not limited to, liquid crystal displays (“LCD”), monochrome displays, color graphics adapter (“CGA”) displays, enhanced graphics adapter (“EGA”) displays, variable graphics array (“VGA”) display, or any other type of display, or any combination thereof. Still further, a touch screen may, in some embodiments, correspond to a display device including capacitive sensing panels capable of recognizing touch inputs thereon. For instance, display component 232 may correspond to a projected capacitive touch (“PCT”), screen. In some embodiments, display component 232 may be an optional component for a voice-enabled device 102. For instance, a voice-enabled device 102 may not include display component 232. Such devices, sometimes referred to as “headless” devices, may output audio, or may be in communication with a display device for outputting viewable content.

In some embodiments, content displayed on display component 232 may be formatted such that contextual entities and lists are able to be analyzed by speech processing system 100 for list resolution and/or anaphora resolution. Context related to the displayed content may include entities associated with a voice-enabled device 102 including, but not limited to, foreground entities (e.g., lists of items, detail pages), background entities (e.g., songs, audio books), and notification entities. The contextual data may be structured into context entity slots, list metadata, and any other additional data available. For example, contextual entity slots may correspond to data used for list resolution and/or anaphora resolution. The contextual entity slots may be specified in domain definitions with corresponding values. The list metadata may include list identifiers, item identifiers for items of a list, and absolute positions of the list for a particular item (e.g., a first item of a list, a second item of a list, etc.). Such additional data may include unique identifiers associated with an object, item prices, quantities, and the like.

In some embodiments, a voice-enabled device 102 may include one or more cameras 230, corresponding to any suitable image capturing component or components capable of capturing one or more images and/or videos. Camera(s) 230 may, in some embodiments, be configured to capture photographs, sequences of photographs, rapid shots (e.g., multiple photographs captured sequentially during a relatively small temporal duration), videos, or any other type of image, or any combination thereof. In some embodiments, a voice-enabled device 102 may include multiple cameras 230, such as one or more front-facing cameras and/or one or more rear facing cameras. Furthermore, camera(s) 230 may be configured to recognize far-field imagery (e.g., objects located at a large distance away from a voice-enabled device 102) or near-field imagery (e.g., objected located at a relatively small distance from a voice-enabled device 102). In some embodiments, the camera(s) may be high-definition (“HD”) cameras, capable of obtaining images and/or videos at a substantially large resolution (e.g., 720p, 1080p, 1080i, 4K, etc.). In some embodiments, camera(s) 230 may be optional for a voice-enabled device 102. For instance, camera(s) 230 may be external to, and in communication with, a voice-enabled device 102. For example, an external camera may be capable of capturing images and/or video, which may then be provided to a voice-enabled device 102 for viewing and/or processing.

In some embodiments, display component 232 and/or camera(s) 230 may be optional for a voice-enabled device 102. For instance, a voice-enabled device 102 may function using audio inputs, and outputting audio in response or causing one or more actions to occur in response, and therefore display component 232 and/or camera(s) 230 may not be included. Furthermore, in some embodiments, a voice-enabled device 102 may not include display component 232 and/or camera(s) 230, but instead may be in communication with display component 232 and/or camera(s) 230. For example, a voice-enabled device 102 may be connected to a display screen via a Wi-Fi (e.g., 802.11 protocol) connection such that visual content sent to a voice-enabled device 102 may be sent to the display screen, and output thereby.

In some embodiments, contextual data may be obtained by computer vision analysis of an object detected by camera(s) 230. For example, in response to speaking the utterance, “Buy this,” a voice-enabled device 102 may cause camera(s) 230 to capture an image. That image may be analyzed to determine what the object is, and the contextual data associated with that objects identify may be determined. For instance, if an individual is holding up a bottle of ketchup, then the computer vision analysis may be able to determine a product name, bar code, and/or any other attribute about the bottle of ketchup from the captured image, and may populate a contextual data structure indicating the determined values (e.g., ‘Item Name’ slot: “Ketchup”).

The voice-enable device 102 may communicate with the speech processing system 100 over one or more networks 150. The one or more networks 150 may include any viable communication technology, such as wired and/or wireless modalities and/or technologies. Networks 150 may include any combination of Personal Area Networks (“PANs”), Local Area Networks (“LANs”), Campus Area Networks (“CANs”), Metropolitan Area Networks (“MANs”), extranets, intranets, the Internet, short-range wireless communication networks (e.g., ZigBee, Bluetooth, etc.), Wide Area Networks (“WANs”)—both centralized and/or distributed—and/or any combination, permutation, and/or aggregation thereof.

As shown in FIG. 2 , a speech processing system 100 may include various subsystems, components, and/or modules including, but not limited to, an ASR system 202, an NLU system 204, domains system 206, a TTS system 208, an inter-domain routing system 210, an intra-domain routing system 212, a contextual data management system 214, a user data store 216, and a processing data store 218. In some embodiments, speech processing system 100 may also include an orchestrator system (not shown) capable of orchestrating one or more processes to be performed by one or more of ASR system 202, NLU system 204, domains system 206, TTS system 208, inter-domain routing system 210, intra-domain routing system 212, as well as one or more additional components, devices, and/or systems associated therewith. Speech processing system 100 may also include computer readable media, including, but not limited to, flash memory, random access memory (“RAM”), and/or read-only memory (“ROM”). Speech processing system 100 may also include various modules that store software, hardware, logic, instructions, and/or commands for speech processing system 100, such as a speaker identification (“ID”) module, or any other module, or any combination thereof.

ASR system 202 may be configured to recognize human speech in detected audio, such as audio captured by a voice-enabled device 102, which may then be transmitted to speech processing system 100. ASR system 202 may include, in one embodiment, one or more processor(s) 252, storage/memory 254, and communications circuitry 256. Processor(s) 252, storage/memory 254, and communications circuitry 256 may, in some embodiments, be substantially similar to processor(s) 220, storage/memory 222, and communications circuitry 224, which are described in greater detail above, and the aforementioned descriptions may apply. Furthermore, in some embodiments, ASR system 202 may include STT system 280. STT system 280 may employ various speech-to-text techniques.

ASR system 202 may transcribe received audio data into text data representing the words of the speech contained in the audio data using STT system 280. The text data may then be used by other components for various purposes, such as executing system commands, inputting data, etc. The different ways a spoken utterance may be transcribed (i.e., the different hypotheses) may each be assigned a probability or a confidence score representing a likelihood that a particular set of words matches those spoken in the utterance. The confidence score may be based on a number of factors including, for example, the similarity of the sound in the utterance to models for language sounds (e.g., an acoustic model), and the likelihood that a particular word which matches the sounds would be included in the sentence at the specific location (e.g., using a language or grammar model). Thus each potential textual representation of the spoken utterance (hypothesis) is associated with a confidence score. Based on the considered factors and the assigned confidence score, ASR system 202 may output the most likely textual representation(s) of the audio data.

ASR system 202 may generate results data in the form of a single textual representation of the speech, an N-best list including multiple hypotheses and respective scores, and/or lattice, for example, which may be sent to NLU system 204 for processing, such as conversion of the text into commands for execution, either by a voice-enabled device 102, speech processing system 100, or by another device, such as a separate device or server capable of performing one or more additional functionalities thereon (e.g., a television capable of outputting video content).

NLU system 204 may be configured such that it determines an intent of an utterance based on the received audio data. NLU system 204 may include processor(s) 252, storage/memory 254, and communications circuitry 256 which, in one embodiment, may be substantially similar to processor(s) 220, storage/memory 222, and communications circuitry 224 of electronic device 102, and the previous description may apply.

NLU system 204 may include a named entity recognition (“NER”) system 272, which may be used to identify portions of text that correspond to a named entity recognizable by NLU system 204. A downstream process called named entity resolution 292 may be configured to link a portion of text to an actual specific known entity. To perform named entity resolution, the system may utilize gazetteer data stored in an entity library storage. The gazetteer data may be used for entity resolution, for example matching ASR results with different entities (such as song titles, contact names, etc.). Gazetteers may be linked to a user account or profile of users accounts data store 216, certain domains (e.g., music or shopping), or may be organized in a variety of other ways.

Generally described, NLU system 204 may take textual input and attempt to make a semantic interpretation of the text. That is, NLU system 204 may be configured to determine a meaning of text data (e.g., based on the individual words represented by the text data) and then implement that meaning. In some embodiments, NLU system 204 may interpret a text string to derive an intent or a desired action of the utterance (e.g., utterance 106) as well as the pertinent pieces of information in the text that allow an action to be completed. For example, if a spoken utterance is processed by ASR system 202 and outputs the text, “call mom,” NLU system 204 may determine that an intent of the utterance is to activate a telephone, or telephone functionality, and to initiate a call with a contact matching the entity “mom”. In some embodiments, NLU system 204 may process several textual inputs related to the same utterance. For example, if ASR system 202 outputs N text segments (as part of an N-best list), then NLU system 204 may process all N outputs.

NLU system 204 may be configured to parse and label, tag, or otherwise annotate text. For example, in the text “call mom,” the word “call” may be tagged as a command (e.g., a command to execute a phone call), and the word “mom” may be tagged as a specific entity and target of the command (e.g., a telephone number for the entity corresponding to “mom” stored in a contact list). Further, NLU system 204 may be used to provide answer data in response to queries, for example using a knowledge base stored within storage/memory 254 of NLU system 204 and/or storage/memory of speech processing system 100.

An intent classification (“IC”) system 274 may parse the query to determine an intent or intents, where the intent corresponds to the action to be performed that is responsive to the query. The intents identified by IC system 274 may be linked to grammar frameworks having fields, also referred to as “slots,” to be filled. Each slot may correspond to a portion of the query text that the system believes corresponds to an entity. For example, if “play music” is an identified intent, a grammar framework or frameworks may correspond to sentence structures such as “Play {Artist Name},” “Play {Album Name},” “Play {Song name},” “Play {Song name} by {Artist Name},” etc. However, to make resolution more flexible, these frameworks may not be structured as sentences, but rather based on associating slots with grammatical tags. As another example, if “Play ‘Song 1’” is an identified intent, a grammar framework may correspond to sentence structures such as “Play {Song 1}.”

NER system 272 may parse the query to identify words as subject, object, verb, preposition, etc., based on grammar rules and/or models, prior to resolving named entities. The identified verb may be used by IC module 274 to identify intent, which is then used by NER system 272 to identify frameworks. A framework for an intent of “play” may specify a list of slots/fields/placeholders applicable to place the identified “object” such as, for example, {Artist Name}, {Album Name}, {Song Name}, {Application Name}, {Anaphoric Term}, and any object modifier (e.g., a prepositional phrase). NER system 272 may then search the corresponding fields in the domain-specific and personalized lexicon(s), attempting to match words and phrases in the query, which are tagged as a grammatical object or object modifier, with those identified in the database(s).

For instance, a query of “Play ‘Song 1’ by ‘Artist 1’” might be parsed and tagged as {Verb}: “Play,” {Object}: “Song 1,” {Object Preposition}: “by,” and {Object Modifier}: “Artist 1.” At this point in the process, “Play” may be identified as a verb based on a word database associated with the music domain, which IC module 274 may determine corresponds to the “play music” intent. No determination has been made as to the meaning of “Song 1” and “Artist 1,” but based on a models, such as a multi-modal model, it may be determined that the text of these phrases relate to the grammatical object (i.e., entity) of the query.

The frameworks linked to the intent may then be used to determine what database fields should be searched to determine the meaning of these phrases, such as searching a user's gazette for similarity with the framework slots. So a framework for a “play music” intent might attempt to resolve the identified object for {Artist Name}, {Album Name}, {Song Name}, and {Application Name}, {Anaphoric Term} and another framework for the same intent might attempt to resolve the object modifier based on {Artist Name}, and resolve the object based on {Album Name} and {Song Name} linked to the identified {Artist Name}. If the search of the gazetteer does not resolve a slot/field using gazetteer data, NER system 272 may search the database of generic words associated with the particular domain. So for instance, if the query was “play songs by ‘Artist 1,’” after failing to determine an album name or song name called “songs” by “Artist 1,” NER system 272 may search the domain vocabulary for the word “songs.” For example, use of the object “songs” may correspond to some or all of the songs associated with a particular artist (e.g., “Artist 1”). In the alternative, generic words may be checked before the gazetteer data, or both may be tried, potentially producing two different results.

The results of the natural language understanding processing may be tagged or labeled to attribute meaning to the query. So, for instance, “Play ‘Song 1’ by ‘Artist 1’” might produce a result of: {Intent}: “play-music,” {Artist Name}: “Artist 1,” {Media Type}: “Song,” and {Song Name}: “Song 1.” As another example, “Play songs by ‘Artist 1’” might produce: {Intent}: “play-music,” {Artist Name}: “Artist 1,” and {Media Type}: Song. Still further, “Add this to my cart’” might produce a result of: {Intent} “add-item-to,” {Anaphoric Term}: “this,” and {List Type} “cart.”

The NLU system 204 may generate multiple intent hypotheses to be considered by downstream processes. In some embodiments, the set of intent hypotheses may be arranged in an N-best list of intents and slots corresponding to the top choices as to the meaning of an utterance, along with scores for each item. For example, for ASR output data representing the utterance “Play Harry Potter,” the NLU system 204 may generate output in the form of an N-best list s of scored intent hypotheses, such as:

(0.93) Intent: play-movie; Title: “Harry Potter and the Sorcerer's Stone”

(0.03) Intent: play-movie; Title: “Harry Potter and the Deathly Hallows Part 2”

(0.02) Intent: play-movie; Title: “Harry Potter and the Deathly Hallows Part 1”

(0.01) Intent: play-music; Title: “Harry Potter Original Motion Picture Soundtrack”

(0.01) Intent: play-audio-book; Title: “Harry Potter and the Sorcerer's Stone”

The NLU system 204 can generate scores for intents and content slots using the text data and other data, such as contextual data. The scores may indicate how likely individual labels are to be the correct labels for individual words of the utterance being processed. In the present example, the utterance “Play Harry Potter” includes three words: “Play,” “Harry,” and “Potter.” The individual words may be labeled using a predetermined set of labels, including different labels for the various intents recognizable by the NLU system 204 and different labels for the content slots that correspond to the various intents.

This process may include semantic tagging, which is the labeling of a word or a combination of words according to their type/semantic meaning. Labeling may be performed using an NER model, alone or in combination with heuristic grammar rules. The NER model may be constructed using techniques such as hidden Markov models, maximum entropy models, log linear models, conditional random fields (“CRF”), or other models configured to generate labeling data (e.g., scores, probabilities, etc. for individual labels) using text data and, in some cases, contextual data.

In some embodiments, the NLU system 204 may include domain-specific recognizers for each of multiple domains, and each of the domain-specific recognizers may include their own NER component 272, IC component 274, etc. For example, the NLU system 204 may include recognizers for a shopping domain, a music domain, a video domain, and a communications domain.

The NLU system 204 may also include a slot filler component 290. The slot filler component 290 can take text from slots and alter it to make the text more easily processed by downstream components. The operations of the slot filler component 290 are typically low latency operations that do not involve heavy operations such as reference to a knowledge base. The purpose of the slot filler component 290 is to replace words with other words or values that may be more easily understood by downstream components. For example, if a textual interpretation represented in the text data 320 included the word “tomorrow,” the slot filler component 290 may replace the word “tomorrow” with an actual date for purposes of downstream processing. Similarly, a word “CD” may be replaced by a word “album” of the words “compact disc.” The replaced words may then be included in the cross-domain N-best list data.

N-best list data may then be sent to an entity resolution component 292. The entity resolution component 292 can apply rules or other instructions to standardize labels or tokens from previous stages into an intent/slot representation. The precise transformation may depend on the domain (e.g., for a travel domain a text mention of “Boston airport” may be transformed to the standard BOS three-letter code referring to the airport). The entity resolution component 292 can refer to an authority source (such as a knowledge base) that is used to specifically identify the precise entity referred to in the entity mention identified in each slot represented in the cross-domain N-best list data. Specific intent/slot combinations may also be tied to a particular source, which may then be used to resolve the text. In the example “play songs by the stones,” the entity resolution component 292 may reference a personal music catalog, Amazon Music account, user account, or the like. The output from the entity resolution component 292 may include altered N-best list data that is based on the cross-domain N-best list represented in the cross-domain N-best list data, but may also include more detailed data (e.g., entity IDs) about the specific entities mentioned in the slots and/or more detailed slot data that can eventually be used by an application 282 which may be incorporated into the same system components or pipeline or may be on a separate device in communication with the NLU system 204. Multiple entity resolution components 292 may exist where a particular entity resolution component 292 may be specific to one or more domains.

The NLU system 204 may produce NLU output data from the N-best list data described above. The NLU output data may include a highest-scoring interpretation from the cross-domain N-best list data, or it may be data representing an N-best list of highest-scoring interpretations. In some embodiments, the NLU system 204 may re-score, bias, or otherwise alter the N-best list data generated by the entity resolution component 292. To do so, the NLU system 204 may consider not only the N-best list data generated by the entity resolution component 292, but may also consider other data. The other data may include a variety of data. For example, the other data may include application rating or popularity data. For example, if one application has a particularly high rating, the NLU system 204 may increase the score of results associated with that particular application. The other data may also include data about applications that have been specifically enabled by the user (as indicated in a user account). NLU output data associated with enabled applications may be scored higher than results associated with non-enabled applications.

An example of processing of an NLU system is described in U.S. Pat. No. 10,515,625, issued on Dec. 24, 2019, which is incorporated by reference herein.

Domains system 206 may, for example, correspond to various action specific applications 282, which are capable of processing various task specific actions and/or performing various functionalities related to the user experience. Domains system 206 may further correspond to first party applications and/or third party applications capable of performing various tasks or actions, or performing various functionalities. For example, based on the context of the audio received from a voice-enabled device 102, speech processing system 100 may use a certain application 282 to generate a response, or to obtain response data, which in turn may be communicated back to a voice-enabled device 102 and/or to another electronic device (e.g., a television). Domains system 206 may also include processor(s) 252, storage/memory 254, and communications circuitry 256. In some embodiments, an application 282 of domains system 206 may be written in various computer languages, such as JavaScript and Java.

TTS system 208 may employ various text-to-speech techniques for presentation to a user (e.g., a spoken response to an utterance). TTS system 208 may also include processor(s) 252, storage/memory 254, communications circuitry 256, and speech synthesizer 284.

Inter-domain routing system 210 may manage routing of utterances to the appropriate domain, as described in greater detail below. Inter-domain routing system 210 may also include processor(s) 252, storage/memory 254, communications circuitry 256, and speech synthesizer 284.

Intra-domain routing system 212 may manage routing of utterances, within a particular domain, to the appropriate subdomain and/or application 282, as described in greater detail below. Intra-domain routing system 212 may also include processor(s) 252, storage/memory 254, communications circuitry 256, and speech synthesizer 284.

Contextual data management system 214 may manage acquisition of contextual data to be used in routing determinations as described in greater detail below. Contextual data management system 214 may also include processor(s) 252, storage/memory 254, communications circuitry 256, and speech synthesizer 284.

User data store 216 may store data representing or otherwise associated with one or more user accounts or user profiles, corresponding to users having an account on speech processing system 100. In some embodiments, data, settings, and/or preferences for each user profile may be stored by user data store 216. For example, the user data store 216 may store data regarding prior user interactions with the speech processing system 100, such as data regarding actions that the speech processing system 100 has performed in response to utterances from a user associated with a particular user profile. As another example, the user data store 216 may store data regarding one or more voice-enabled devices 102 associated with a user profile, such as device identifiers, phone numbers, network addresses, version information, data regarding capabilities and installed applications, and the like. In some embodiments, user data store 216 may include a list of media items currently stored within an individual's registered account or user profile. For example, a list of music or videos purchased or obtained by an individual may be stored within the individual's user profile on user data store 216, which may be accessed by the individual when the individual seeks to hear a particular song or songs, or view a particular video or videos. User data store 216 may also include a listing of all applications currently enabled for each user profile. In some embodiments, NLU system 204 may receive indications of which applications are currently enabled for a particular user profile or account, such that NLU system 204 is aware of which rules and capabilities that speech processing system 100 is able to perform for the particular user profile or account. In some embodiments, user data store 216 may store a voice signal, such as voice biometric data, for a specific user profile. This may allow speaker identification techniques to be used to match a voice to voice biometric data associated with a specific user profile. The examples of data stored in the user data store 216 are illustrative only, and are not exhaustive, required, or limiting of the data that may be stored in the user data store 216.

Processing data store 218 may store data to be used during the processing of an utterance, such as contextual data obtained and/or generated by the contextual data management system 214, as described above and in greater detail below. Such data may be used during routing determinations, for example those made by the intra-domain routing system 212. In some embodiments, processing data store 218 may store data to be used offline, such as after (or without) processing an utterance. For example, data regarding the utterance, contextual data items obtained during processing of the utterance, feedback, etc. may be stored in the processing data store 218 and used during offline processes such as training a model used by one or more components of the speech processing system 100.

Although each of ASR system 202, NLU system 204, domain systems 206, TTS system 208, inter-domain routing system 210, intra-domain routing systems 212, contextual data management system 214, user data store 216, and processing data store 218 may each include instances of processor(s) 252, storage/memory 254, and communications circuitry 256, and those instances of processor(s) 252, storage/memory 254, and communications circuitry 256 within each of ASR system 202, NLU system 204, domain systems 206, TTS system 208, inter-domain routing system 210, intra-domain routing systems 212, contextual data management system 214, user data store 216, and processing data store 218 may differ. For example, the structure, functionality, and style of processor(s) 252 within ASR system 202 may be substantially similar to the structure, functionality, and style of processor(s) 252 within NLU system 204, however the actual processor(s) 252 need not be the same entity.

Domain Routing

FIG. 3 is a diagram of illustrative data flows and interactions between components of the speech processing system 100 during the processing and routing of an utterance to an application for response or other action. Portions of FIG. 3 will be described with further reference to FIG. 4 , which is a flow diagram of an illustrative process that may be executed by an intra-domain routing system 212 to generate routing confidence evaluations for the utterance.

As shown, an utterance may be processed using a set of natural language processing actions, such as those performed by the ASR system 202 and NLU system 204, to generate one or more intents, such as an N-best list 300. Before, during, and after the course of generating the intent(s), various contextual data items 302 may be obtained and/or generated by the contextual data management system 214. An example process for obtaining and/or generating contextual data items for use by one or more intra-domain routing systems 212 is described in greater detail below.

The inter-domain routing system 210 can determine which domains are associated with individual intents of the N-best list 300. In some embodiments, individual domain systems 206 may be assigned, registered, or otherwise associated with different intents. The inter-domain routing system 210 may determine which domain systems 206 are associated with each of the intents in the N-best list 300 (or a subset thereof). The inter-domain routing system 210 may generate and send confidence requests 304 to the intra-domain routing systems 212 for the determined domain systems 206. For example, the N-best list 300 may include five intents, ranked 1-5, where 1 is the highest-ranked intent and 5 is the fifth-highest ranked intent. A particular domain system 206 may be registered to handle two of the five intents (e.g., the intents ranked 1 and 4), another domain system may be registered to handle one of the intents (e.g., the intent ranked 2), and so on. The inter-domain routing system 210 can generate a confidence request 304 to the intra-domain routing system 212 for the domain 206 registered to handle the intents ranked 1 and 4. The confidence request 304 may be a request for the intra-domain routing system 212 to evaluate whether the corresponding domain 206, or a specific application 282 thereof, is the proper entity to respond to the user utterance. A confidence request may include the intents, and in some cases may include additional information, such as ranking information or the like.

Upon receipt of a confidence request 304, the intra-domain routing system 212 can identify one or more routing confidence providers 320 to generate routing confidence evaluations that will be used to assign a specific application 282 to generate a response to the utterance, or to determine that no application of the domain is to generate a response. Although the routing confidence providers 320 are shown in FIG. 3 as being external to the intra-domain routing system 212, in some embodiments, any or all of the routing confidence providers 320 may be integrated into the intra-domain routing system 212. For example, the intra-domain routing system 212 may include routing confidence providers for each application of the corresponding domain, or for a subset thereof. As another example, one or more routing confidence providers may be hosted by a computing system outside of the intra-domain routing system 212, such as a computing system on which a corresponding application is implemented. Illustratively, the domain may be configured with an application programming interface (“API”) that allows third-party entities to provide applications and corresponding routing confidence providers for a particular domain.

FIG. 4 is a flow diagram of an illustrative process 400 that may be performed by an intra-domain routing system 212 to generate routing confidence evaluations in response to confidence requests 304. The process 400 begins at block 402. When the process 400 is initiated, a set of executable program instructions stored on one or more non-transitory computer-readable media (e.g., hard drive, flash memory, removable media, etc.) may be loaded into memory (e.g., random access memory or “RAM”) of a computing device and executed. For example, executable instructions may be loaded into memory 254 of a computing device of the intra-domain routing system 212 and executed by one or more processors 252. In some embodiments, the process 400 or portions thereof may be implemented on multiple processors, serially or in parallel.

At block 404, the intra-domain routing system 212 may obtain the confidence request 304 from the inter-domain routing system 210. In some embodiments, the confidence request may be obtained by, or provided to, a particular component of the intra-domain routing system 212, such as a master speechlet 310 for the corresponding domain 206.

At block 406, the master speechlet 310 may use another component of the intra-domain routing system 212, such as routing decider 314, to determine the routing confidence providers 320 from which to obtain routing confidence evaluations. For example, a particular domain system 206 may be associated with any number of subdomains and/or applications 282. A routing confidence provider 320 may be implemented for each individual subdomain or application 282, or various subsets thereof. Individual routing confidence providers 320 may be configured to generate routing confidence evaluations (e.g., scores) indicating degrees of confidence that a particular subdomain or application 282 is the appropriate entity to respond to an utterance. The routing decider 314 or some other component of the intra-domain routing system 212 may identify the routing confidence providers 320 from which to obtain routing confidence evaluations based on a predetermined or dynamically-determined mapping of intents 300 to routing confidence providers 320. For each intent 300 in the confidence request 304, the routing decider 314 may identify the routing confidence provider(s) 320 from which to obtain a routing confidence evaluation.

At block 408, the routing decider 314 or some other component of the intra-domain routing system 212 may obtain the contextual data items 302, if any, to be provided to the routing confidence providers 320. In some embodiments, a mapping may be used to determine the specific contextual data items that a given routing confidence provider 320 is to be provided with. For example, one routing confidence provider 320 may make a routing confidence evaluation using location data associated with the voice-enabled device 102 and capability data representing capabilities of the voice-enabled device, while another routing confidence provider 320 may make a routing confidence evaluation based on particular entities recognized in the utterance and particular content items displayed by the voice-enabled device 102 when the utterance was made. The routing decider 314 may obtain the contextual data items mapped to each of the routing confidence providers 320. In some embodiments, the contextual data items may be obtained from the processing data store 218, from the contextual data management system 214, and/or from other sources.

At block 410, the routing decider 314 can obtain routing confidence evaluations from the identified routing confidence providers 320. The routing decider 314 may generate requests, commands, or other communications to the routing confidence providers 320, and may include contextual data items 302 in the same communication or may provide access to the contextual data items 302 is some other manner (e.g., by providing a memory or network address of the location from which the routing confidence providers 320 can obtain the contextual data items 302). In some embodiments, the routing confidence providers 320 can obtain the contextual data items 302 directly from the processing data store 218, contextual data management system 214, or other source without receiving or otherwise being provided access to the contextual data items 302 from the routing decider 314. Individual routing confidence providers 320 may make routing confidence evaluations in a variety of ways.

In some embodiments, a routing confidence provider 320 may apply a set of one or more deterministic rules. For example, a set of rules may include applying a particular score or factor if the intent being evaluated is one intent, and a different score or factor if the intent is a different intent. As another example, a score or factor may be used depending upon the ranking of the intent within the N-best list (e.g., if the ranking is relatively low, then the confidence evaluation may be lower than if the ranking was relatively high). The same, additional, and/or alternative scores and/or factors may be incorporated depending upon the values of any contextual data items 302 being considered (e.g., geolocation of the voice-enabled device 102, geographic distance of the voice-enabled device 102 from a point of interest, content displayed by the voice-enabled device 102 when the utterance was made, individual words or phrases present in the utterance, historical usage by an active user profile, content catalog associated with the active user profile, etc.). The routing confidence provider 320 may apply the various scores, factors, calculations, and the like based on the set of deterministic rules, and arrive at an output routing confidence evaluation. The routing confidence evaluation may be a score, such as a score between a minimum (representing a minimum degree of confidence that the utterance is properly handled by an application associated with the routing confidence provider 320) and a maximum (representing a maximum degree of confidence). In some embodiments, the routing confidence evaluation may involve generating a classification into one or more possible classes, such as a first class indicating a low degree of confidence, a second class indicating a high degree of confidence, and a third class indicating a moderate degree of confidence associated with ambiguity.

In some embodiments, a routing confidence provider 320 may apply a statistical model or some other non-deterministic calculation. For example, a statistical model may be derived from a set of observed and/or synthetic data. Application of the statistical model may include obtaining or deriving input values representing the intent being evaluated, the ranking of the intent within the N-best list, the values of any contextual data items 302 being considered, etc. The routing confidence provider 320 may apply the various scores, factors, calculations, and the like based on the statistical model and arrive at an output routing confidence evaluation. The routing confidence evaluation may be a score, such as a score between a minimum and a maximum, a classification into one or more possible classes, etc.

In some embodiments, a routing confidence provider 320 may use a combination of deterministic rules and a statistical model to arrive at a routing confidence evaluation. In some embodiments, additional and/or alternative routing confidence evaluation methods may be used. The example routing confidence evaluation methods described herein are illustrative only, and are not intended to be limiting, required, or exhaustive.

At decision block 412, the routing decider 314 or some other component of the intra-domain routing system 212 may determine whether the routing confidence evaluation(s) received from the routing confidence provider(s) 320 indicate ambiguity. If so, the process 400 may proceed to block 414 where a response to the confidence request indicating ambiguity may be generated. Otherwise, if the routing confidence evaluations do not indicate ambiguity, the process 400 may proceed to decision block 416.

In some embodiments, identification of ambiguity may be based on whether any confidence evaluation made by a routing confidence provider 320 indicates ambiguity. For example, if the routing evaluation is a score between two extremes indicating lowest and highest confidence, respectively, then a score that is at least a threshold distance from both extremes (e.g., in the middle 50% of the range, in the middle 33% of the range, etc.) may trigger identification of an ambiguity. As another example, if the confidence evaluation is one of three classes indicating low, high, and moderate confidence, respectively, then an evaluation in the moderate class may trigger identification of an ambiguity. In some embodiments, identification of ambiguity may be based on whether a highest confidence evaluation, of all confidence evaluations requested by the routing decider 314, indicates ambiguity.

At block 414, the routing decider 314 or some other component of the intra-domain routing system 212 may generate a response to the confidence request based on the identification of the ambiguity. In some embodiments, the response to the confidence request may indicate that an ambiguity resolution component 312 of the intra-domain routing system 212 is the proper entity to respond to the utterance. The ambiguity resolution component 312 may be configured to resolve routing ambiguities that remain after (or were introduced during) ASR, NLU, and other processes. The ambiguity resolution component 312 may resolve ambiguity in interpreting the utterance and determine a destination entity (subdomain or application) to respond. For example, the ambiguity resolution component 312 may perform non-interactive engagement with the user in resolving the ambiguity by providing a relevant hint/suggestion and enabling the user to re-phrase. The re-phrased utterance may then be handled using the utterance processing described above (e.g., handled as though the prior utterance did not occur) without being directed back to the ambiguity resolution component 312. As another example, the ambiguity resolution component 312 may conduct an interactive engagement with the user (e.g., a multi-turn dialog) to resolve the ambiguity through clarifications and/or confirmations. In this case, the user's responses may be directed back to the ambiguity resolution component 312 as part of the multi-turn dialog management by the ambiguity resolution component 312. Illustratively, the interactive engagement may involve presenting options to the user, such as two or more possible applications (e.g., corresponding to the two or more highest routing confidence evaluations) and asking the user to choose one. As a further example, the ambiguity resolution component 312 may obtain additional contextual data items 302 that may not have been available during the initial routing confidence evaluation process, and may use those additional contextual data items 302 to resolve the ambiguity without the need for additional user input (e.g., by adjusting or overriding one or more routing confidence evaluations).

At decision block 416, the routing decider or some other component of the intra-domain routing system 212 may determine whether or not the routing confidence evaluations are indicative of a subdomain or application, of the domain 206 for which the intra-domain routing system 212 is generating routing confidence evaluations, being the proper entity for responding the utterance. If so, the process 400 may proceed to block 418 where the routing decider 314 or some other component of the intra-domain routing system 212 may generate a response to the confidence request indicating the subdomain or application of the domain 206 for which there is a high degree of confidence in being the proper entity for responding to the utterance. Otherwise, the process 400 may proceed to block 420 where the routing decider 314 or some other component of the intra-domain routing system 212 may generate a response to the confidence request indicating that no subdomain or application of the domain 206 is the proper entity for responding to the utterance.

At block 422, the intra-domain routing system 212 may provide the output generated above to the inter-domain routing system 210 in response to the confidence request. The process 400 may terminate at block 424.

FIG. 5 is a diagram of a multi-tier domain 206 that includes multiple applications 282. The process 400 may determine that each of the applications 282A, 282B, 282C is the most appropriate application to respond to the utterance, depending upon the contextual data that is obtained and used to make routing confidence evaluations. Illustratively, the utterance 106 is the same utterance from the example in FIG. 1 : “Where can I find coffee?” The three example applications are a physical store locator application 282A, an in-store aisle location application 282B, and an online shopping application 282C. If the utterance 106 is made and processed in connection with a first set of contextual data (e.g., location information indicating the utterance was made outside the user's 104 home and outside any store), then the physical store location application 282A may be the most appropriate application to respond to the utterance 106. If the utterance 106 is made and processed in connection with a second set of contextual data (e.g., location information indicating the utterance 106 was made in a store), then the in-store aisle location application 282B may be the most appropriate application to respond to the utterance 106. If the utterance 106 is made and processed in connection with a third set of contextual data (e.g., content presentation information indicating the user is browsing items for purchase online), then the online shopping application 282B may be the most appropriate application to respond to the utterance 106.

Early Invocation and Contextual Data Generation

FIG. 6 is a diagram of illustrative data flows and interactions between components of the speech processing system 100 for early invocation of contextual data generation actions during processing of an utterance. Portions of FIG. 6 will be described with further reference to FIG. 7 , which is a flow diagram of an illustrative process that may be executed by the contextual data management stem 214 to generate contextual data associated with an utterance, and FIG. 8 , which is a diagram of illustrative data flows and interactions between components of a contextual data management system 214 during early invocation of contextual data generation actions.

As shown in FIG. 6 and described in greater detail above, an utterance may be processed using a set of natural language processing actions, such as those performed by the ASR system 202 and NLU system 204, to generate one or more intents. The inter-domain routing system 210 may generate one or more confidence requests 304 based on the intents.

In some cases, the natural language processing actions performed by the ASR system 202 and NLU system 204 may cause or experience a relatively high degree of latency. To reduce or eliminate additional user-perceived latency that may be caused by obtaining and/or generating contextual data items 302 for use in routing confidence evaluations, the contextual data items 302 may be obtained and/or generated proactively, without necessarily waiting for the natural language processing actions to be completed. For example, before, during, and after the course of generating the intent(s), various contextual data items 302 may be obtained and/or generated by the contextual data management system 214. The points at which the contextual data management system 214 receives and/or generates contextual data items may be referred to as integration points.

FIG. 6 shows an integration point triggered at [I] which causes the contextual data management system 214 perform various data aggregation and/or early invocation of processing. When an integration point is triggered, it may cause execution of the contextual data management system 214 to process or store data, or to otherwise initiate early invocation of other processes. Advantageously, execution of the contextual data management system 214 triggered at the integration point may proceed in parallel or otherwise asynchronously with at least a portion of the set of natural language processing actions being performed on the utterance.

In some embodiments, an integration point may be implemented before invocation of the ASR system 202. For example, an identifier of the voice-enabled device 102, an identifier of an active user profile associated with the utterance, an identifier of a geographic location of the voice-enabled device 102, and/or various other data items may be obtained with or are otherwise associated with the utterance. The speech processing system 100 may trigger the integration point based on obtaining such data.

In some embodiments, an integration point may be implemented during execution of the NLU system 204. For example, the NLU system may generate one or more preliminary semantic representations of the utterance being processed, including intents with a subset of slots filled with entities. The NLU system 204 may initiate an entity resolution process to resolve one or more the entities (e.g., to determine whether the candidate entities are present in one or more catalogs or other data stores). An integration point may be implemented at the entity resolution stage, and one or more preliminary semantic representation of the utterance may be provided to the contextual data management system 214 for further processing, storage, or the like.

The example integration points described herein are illustrative only, and are not intended to be limiting, required, or exhaustive. In some embodiments, integration points may be implemented at other portions of utterance processing, such as at any point where data is generated or obtained (e.g., to be processed further or provided to another downstream process). Illustratively, any time data is generated or obtained during or otherwise in connection with utterance processing, the contextual data management system 214 may execute to store the data, obtain new data using the data, process the data to generate new data, or cause early invocation of another process. By invoking data aggregation functions and other functions at an early point and performing them in parallel with other processing of the utterance, any prerequisite operations for subsequent processes may be completed by the time the subsequent processes are initiated (e.g., the process of determining routing responsibility for responding to the utterance), thereby reducing user perceived latency (e.g., delay in receiving a response to the utterance).

For example, at [II] the contextual data management system 214 may employ a model evaluation component 600 to use a model, such as a machine learning model or other probabilistic model, to evaluate one or more currently-available data items and make a prediction, classification, or the like. As another example, at [III] the contextual data management system 214 may use an execution service 602 to precompute a contextual data item. The perfected, precomputed, or otherwise pre-generated contextual data items may be stored at [IV] in a processing data store 218 for access by subsequent processes, or in an internal data store of the contextual data management system 214 to be requested during subsequent processes.

FIG. 7 is a flow diagram of an illustrative process 700 that may be performed by the contextual data management system 214 for data aggregation and/or early invocation of processing. The process 700 begins at block 702. When the process 700 is initiated, a set of executable program instructions stored on one or more non-transitory computer-readable media (e.g., hard drive, flash memory, removable media, etc.) may be loaded into memory (e.g., random access memory or “RAM”) of a computing device and executed. For example, executable instructions may be loaded into memory 254 of a computing device of the contextual data management system 214 and executed by one or more processors 252. In some embodiments, the process 700 or portions thereof may be implemented on multiple processors, serially or in parallel.

At block 704, an integration point may be triggered. Triggering of the integration point may cause execution of the contextual data management system 214. Execution of the contextual data management system 214 may be triggered any number of times at any number of integration points during utterance processing, as indicated by the recurrence arrow. The processing executed by the contextual data management system 214 in response to integration points being triggered may occur serially, in parallel, or asynchronously as needed. In addition, the processing for some integration points may operate independently of the processing for other integration points.

At block 706, the contextual data management system 214 may obtain initial data associated with the integration point. Initial data may include data generated or obtained during utterance processing prior to or upon reaching the integration point. For example, if the integration point that was triggered to initiate the current iteration of the process 700 (the “current integration point”) is at utterance intake or otherwise prior to ASR processing, the initial data may include an identifier of the voice-enabled device 102, an identifier of an active user profile, etc. As another example, if the current integration point is at the point of entity resolution during NLU processing, the initial data may include preliminary NLU results such as semantic representations of intent and at least a subset of corresponding entities.

At block 708, the contextual data management system 214 can evaluate the initial data and any data generated or obtained in connection with prior iterations of the process 700 during processing of the current utterance (collectively, the “currently-available data”) to determine one or more contextual data actions to be performed. In some embodiments, as shown in FIG. 8 , the contextual data management system 214 may include a registry 802 of contextual data actions to be performed using the currently-available data. For example, if the currently-available data includes geolocation data and a user profile identifier, the registry may indicate that a contextual data item is to be generated representing whether the user is at their home. As another example, if the currently-available data includes preliminary NLU results, the registry may indicate that a contextual data item is to be generated representing whether the user is likely making an utterance that is a continuation of a prior utterance (e.g., a refinement of a search) or unrelated to any prior utterance (e.g., an entirely new search).

The mechanism by which the registry 802 indicates the contextual data actions to be performed may be based on data or function signatures, such as those including annotations. In some embodiments, the registry may store a listing of function signatures (e.g., Java function signatures) decorated with annotations to indicate data on which the functions are dependent (e.g., data that must be currently available to execute the function). When an integration point is triggered, an orchestrator component 800 of the contextual data management system 214 may review data in the registry 802 and find any functions that are able to be executed using the currently-available data.

At decision block 710, the orchestrator 800 or some other component of the contextual data management system 214 may determine whether to prefetch data using the currently-available data. If so, the process 700 may proceed to block 712. Otherwise, the process 700 may proceed to decision block 714.

At block 712, the orchestrator 800 or some other component of the contextual data management system 214 can initiate prefetching of a contextual data item using the currently-available data. For example, the orchestrator 800 may perform a gazetteer lookup using one or more of the currently-available data items. In some embodiments, the results of the lookup may be stored in an internal data store 804, where it is maintained as currently-available data item for future contextual data generation processes and/or provided to other components of the speech processing system 100 during subsequent processing (e.g., for routing determinations). In some embodiments, the results of the lookup may be stored in a processing data store 218 external to the contextual data management system 214, where it is made accessible to other components of the speech processing system 100 during subsequent processing (e.g., for routing determinations).

In some embodiments, the process 700 may proceed asynchronously. For example, after initiating one or more prefetching operations in block 712, the process 700 may proceed to decision block 714 without necessarily waiting for the prefetching operation(s) to complete. When the prefetching operation(s) initiated in block 712 have completed, the process 700 may proceed to decision block 718 potentially in parallel with, or asynchronous to, the execution of decision block 714, block 716, etc.

At decision block 714, the orchestrator 800 or some other component of the contextual data management system 214 may determine whether to precompute data using the currently-available data. If so, the process 700 may proceed to block 716. Otherwise, the process 700 (or one thread of execution thereof) may terminate at block 720.

At block 716, the contextual data management system 214 can initiate precomputation of a contextual data item using the currently-available data. The precomputed contextual data item may be stored in the data store 804 internal to the contextual data management system 214, or in a processing data store 218 external to the contextual data management system 214. In some embodiments, a model invoker 806 may use a model or cause an external model evaluation component 600 to use a model, such as a machine learning model or other probabilistic model, to evaluate one or more currently-available data items and make a prediction, classification, or the like. For example, the model invoker 806 may generate a classification of the currently-available data as indicative of a search refinement or a new search. In some embodiments, a runtime hosting environment 808 may precompute a contextual data item or cause an external execution service 602 to precompute the contextual data item. For example, the runtime hosting environment 808 may obtain scores for the top two intents of an N-best list, and compute a difference between the scores. As another example, an external execution service 602 may precompute embeddings, such as Bidirectional Encoder Representations from Transformers (“BERT”) embeddings, that will be used by subsequent processes.

In some embodiments, the process 700 may proceed asynchronously. For example, after initiating one or more precomputation operations in block 716, one thread of execution of the process 700 may terminate at block 720 without necessarily waiting for the precomputation operation(s) to complete. When the precomputation operation(s) initiated in block 716 have completed, the process 700 may proceed to decision block 718 potentially in parallel with, or asynchronous to, the execution other portions of the process 700.

At decision block 718 the orchestrator 800 or some other component of the contextual data management system 214 can determine whether there is further contextual data to prefetch and/or precompute based on data prefetched and/or precomputed during the current iteration of the process 700. If so, the process 700 may return to block 708. Otherwise, the process 700 may terminate.

In some embodiments, the process 700 may be conceptualized as building a data graph in which initial data is obtained, additional data is fetched, computed, or otherwise generated based on the available data, and then further data is fetched, computed, or otherwise generated based on the additional data, and so on. In this way, the process 700 may be a recursive process in which a single integration point causes expansion of the data graph by multiple data items, levels, etc. In some embodiments, a prior recursive instance of the process 700 may be ongoing when a subsequent integration point during utterance processing is reached and another instance of the process 700 is invoked. In this way, the process 700 may be performed in parallel or otherwise asynchronously with respect to other instances of the same process 700.

Returning to FIG. 6 , an intra-domain routing system 216 may, in response to a confidence request received at [V], obtain contextual data items at [VI] for use in generating routing confidence evaluations, as described in greater detail above. Once a routing decision has been made, an application 282 may be assigned at [VII] to generate a response to the utterance. In some embodiments, the application 282 may access contextual data items at [VIII] as part of response generation process or otherwise during the course of management a customer experience (e.g., during a multi-turn dialog).

Routing of Utterances with Multi-Domain Triggers

FIG. 9 is a diagram of an illustrative multi-domain, multi-tier hierarchical architecture 900 of intent processing applications. As shown, a particular domain 206A may include one or more applications, such as applications 282A, 282B, and 282C. In some embodiments, the domain 206A may include a subdomain 902A into which one or more applications may be integrated or with which one or more applications may otherwise be associated, such as applications 282A and 282B as shown. The same domain 206A may include other applications, such as application 282C, that are not part of a subdomain.

The multi-domain, multi-tier architecture 900 may include other domains that have the same or a different structure. For example, domain 206B that has multiple subdomains, such as subdomains 902B and 902C. As another example, domain 206C does not include a subdomain but does include multiple applications, such as applications 282D and 282E.

The different domains may be structured and organized such that applications that are associated with a particular subject matter (e.g., shopping, communications, etc.), or that are otherwise configured to process a particular type or group of intents (e.g., buy-item, browse-item, etc.), are within the same domain. In some embodiments, each domain may be associated with a set of intents that the application(s) of the domain are configured to process, and the associations may be registered with or otherwise available to other higher-level routing components of the speech processing system 100, such as the inter-domain routing system 210. When a particular intent is recognized as a possible interpretation of an utterance, a confidence request is sent to the intra-domain routing system(s) 212 for the domain(s) associated with that intent. The intra-domain routing system 212 provides an evaluation of whether the associated domain is to handle processing of the utterance and, if so, the specific application to be assigned to generating a response to the utterance or otherwise process an intent.

Structuring the multi-domain, multi-tier architecture 900 in the manner shown and described herein may provide various benefits beyond mere organization. For example, placing similar applications into the same domain can allow for domain-level routing determinations (e.g., fulfilment request responses) that indicate the domain as a whole (e.g., at least one application thereof) is likely capable of processing a given utterance intent. Such domain-level evaluations can in some cases be performed separately from, and more quickly than, waiting for routing confidence evaluations associated with multiple applications of the domain. Thus, latency experienced when making routing determinations can be reduced when such an initial routing determination is made. More fine-grained routing decisions may be made within the domain, such as when an intent is assigned to an ambiguity resolution component 312 of a domain that performs disambiguation among multiple possible applications, or when other routing arbitration is performed. As another example benefit of the multi-domain, multi-tier architecture 900, the functionality of some subsets of applications can be grouped into one or more subdomains. Routing confidence evaluations and other determinations for such a subset of applications can be provided by a single source, such as a single routing confidence provider for the subdomain.

With reference to one specific, non-limiting embodiment, domain 2060A may be a shopping domain including a plurality of applications 282A-282C configured to perform item search and acquisition operations. Domain 206B may be a recipe domain including a plurality of subdomains 902B, 902C and/or applications (not shown) configured to perform recipe search, presentation, and interaction operations. Domain 206A may be a smart home domain including a plurality of applications 282D, 282E configured to perform smart home device management and interaction operations.

Some utterances may be reasonably interpreted as any of multiple different intents in multiple different domains, and are therefore associated with an undesirably high likelihood of false routing determinations (e.g., false acceptances and false rejections). For example, an intra-domain routing system 212 for the shopping domain 206A may determine with a high degree of confidence that the utterance “Show security cameras,” as represented by a “shopping-search-item” intent, is properly handled by a shopping-related search and display application, while an intra-domain routing system 212 for the smart home domain 206C also determines with a high degree of confidence that the same utterance, as represented by a “smart-home-display-video” intent, is properly handled by a home video camera display application. To address this issue, an intra-domain routing system 212 may implement a set of deterministic rules or a statistical model configured to consider various contextual data signals, including contextual signals associated with other domains, when making routing evaluations for utterances that have a comparatively high likelihood of ambiguity and false routing determinations. Such utterances may include carrier phrases that are indicative of a multi-domain request. In some embodiments, the carrier phrase may be or include a multi-domain trigger like “Show.”

FIG. 10 illustrates an example statistical model 1000, also referred to simply as a model, that may be trained and used to make routing decisions for utterances that include multi-domain triggers like “Show.” Advantageously, the model 1000 may receive a variety of contextual signals, in some cases including contextual signals associated with other domains, to determine whether the current domain is the proper domain to respond to the utterance. By considering a more comprehensive set of contextual signals, including cross-domain contextual signals, the occurrence of false acceptances and false rejections can be reduced.

In some embodiments, as shown, the model may be used to analyze the intent 1002 that is the hypothetical interpretation of the utterance, and one or more contextual signals such as: domain negative gazetteer data 1004; domain on-screen item similarity score data 1006; extra-domain on-screen item similarity score data 1008; top-scoring intent identification data 1010; second-scoring intent identification data 1012; top two intent scoring differential data 1014; device identification data 1016; other contextual signals; or any combination thereof.

The intent 1002 is the intent for which the model 1000 is being used to determine whether it is properly handled by a given domain. In the description that follows, this intent will be referred to as the current intent, the utterance for which the intent is a hypothetical interpretation will be referred to as the current utterance, and the domain for which the evaluation is being performed will be referred to as the current domain. For example, the intent may be a “shopping-search-item” intent for the shopping domain 206A.

The domain negative gazetteer data 1004 may be generated using a set of terms that are indicative of utterances that are not associated with the current domain. In the case of shopping domain 206A, the set of terms may include terms that are typically not included in shopping-related utterances. If the current utterance includes a term in this set of terms, the domain negative gazetteer data 1004 can be set to a value indicating such. For example, the value of the domain negative gazetteer data 1004 may be a binary value in which 1 indicates the presence of a term likely to indicate the utterance is not associated with the current domain, and 0 indicates absence of any term likely to indicate the utterance is not associated with the current domain. In some embodiments, the domain negative gazetteer data 1004 may be generated by the contextual data management system 214. For example, an integration point may be triggered during or after processing by the ASR system 202, and the contextual data management system 214 may receive a term or listing of terms recognized in the utterance. The contextual data management system 214 may then search the set of terms, or cause a separate system or process to search the set of terms, for generating the domain negative gazetteer data 1004 for the current domain.

The domain on-screen item similarity score data 1006 may be generated using data regarding the items associated with the current domain that are presented on a display screen 232 of the voice-enabled device 102 when the utterance was made. Items displayed on the display screen 232 may have textual labels. If any items displayed on the display screen 232 are associated with the current domain, then terms of the utterance may be evaluated with respect to those textual labels to determine whether they are the same or similar, or to determine the degree to which the terms are the same or similar to the textual labels. In some embodiments, similarity may be determined using one or more metrics for the differences between strings or other sequences, such as a Levenshtein distance, a distance between embeddings representing the strings, etc. In some embodiments, the domain on-screen item similarity score data 1006 may be generated by the contextual data management system 214. For example, an integration point may be triggered during or after processing by the ASR system 202, and the contextual data management system 214 may receive a listing of terms recognized in the utterance. The contextual data management system 214 (or some other system or process initiated by the contextual data management system 214) may then obtain data representing the items associated with the current domain, if any, displayed on the display screen 232. The data regarding the displayed items may be received from the voice-enabled device 102, or the data may be obtained from a data store of the speech processing system 100 where it was stored when display data was sent to the voice-enabled device 102 for display. The contextual data management system 214 (or some other system or process initiated by the contextual data management system 214) may evaluate the data regarding terms in the current utterance against the data regarding the displayed items associated with the current domain to generate domain on-screen item similarity score data 1006. Illustratively, a higher score may be indicative a higher likelihood that the utterance includes terms that are the same as, or similar to, items displayed on the display screen 232 associated with the current domain.

The extra-domain on-screen item similarity score data 1008 may be generated using data regarding the items associated with a domain other than the current domain that are presented on a display screen 232 of the voice-enabled device 102 when the utterance was made. If any items displayed on the display screen 232 are associated with a domain other than the current domain, then terms of the utterance may be evaluated with respect to those textual labels to determine whether they are the same or similar, or to determine the degree to which the terms are the same or similar to the textual labels. In some embodiments, similarity may be determined using one or more metrics for the differences between strings or other sequences, such as a Levenshtein distance, a distance between embeddings representing the strings, etc. In some embodiments, the extra-domain on-screen item similarity score data 1008 may be generated by the contextual data management system 214. For example, an integration point may be triggered during or after processing by the ASR system 202, and the contextual data management system 214 may receive a listing of terms recognized in the utterance. The contextual data management system 214 (or some other system or process initiated by the contextual data management system 214) may then obtain data representing the items associated with a domain other than the current domain, if any, displayed on the display screen 232. The data regarding the displayed items may be received from the voice-enabled device 102, or the data may be obtained from a data store of the speech processing system 100 where it was stored when display data was sent to the voice-enabled device 102 for display. The contextual data management system 214 (or some other system or process initiated by the contextual data management system 214) may evaluate the data regarding terms in the current utterance against the data regarding the displayed items associated with a domain other than the current domain to generate extra-domain on-screen item similarity score data 1008. Illustratively, a higher score may be indicative a higher likelihood that the utterance includes terms that are the same as, or similar to, items displayed on the display screen 232 associated with a domain other than the current domain.

The top-scoring intent identification data 1010 may represent the top-scoring intent generated by the NLU system 204, or a particular aspect of the top-scoring intent. As described herein, the NLU system 204 may generate an N-best list of intents and associated confidence scores for an utterance. Each intra-domain routing system 212 may receive confidence requests for only the intents registered to the domain with which the intra-domain routing system 212 is associated. Thus, the intra-domain routing system 212 for the current domain may not necessarily receive the top-scoring intent from the N-best intents (e.g., h1), but may instead receive the second-to-top scoring intent (e.g., h2) and/or lower-scoring intents. Top-scoring intent identification data 1010 can be used to signal to the intra-domain routing system 212 whether it received the top-scoring intent, the identity of the top-scoring intent, etc. For example, the top-scoring intent identification data 1010 may be used to indicate whether the top-scoring intent is an intent of the current domain that is often the subject of utterances with multi-domain triggers, such as a “shopping-search-item” intent for the shopping domain 206A. In some embodiments, the top-scoring intent identification data 1010 may be generated by the contextual data management system 214. For example, an integration point may be triggered after processing by the NLU system 204 generates an N-best list of intents, and the contextual data management system 214 may receive the N-best list or a subset thereof, such as the top-scoring or two top-scoring intents. The contextual data management system 214 (or some other system or process initiated by the contextual data management system 214) may then generate top-scoring intent identification data 1010.

The second-to-top-scoring intent identification data 1012 may represent the second-to-top-scoring intent generated by the NLU system 204, or a particular aspect of the second-to-top-scoring intent. Similar to the top-scoring intent identification data 1010, the second-to-top-scoring intent identification data 1012 may identify the second-to-top scoring intent (e.g., h2) of an N-best list. In some embodiments, the second-to-top-scoring intent identification data 1012 may be generated by the contextual data management system 214 in a manner similar to that described above with respect to the top-scoring intent identification data 1010.

The top two intent scoring differential data 1014 may represent the difference in scores generated for the top-scoring intent and second-to-top-scoring intent. For example, the scores used to rank the top-scoring intent (e.g., h1) and second-to-top-scoring intent (e.g., h2) in the N-best list may be used to calculate a difference. The difference may be reflected in the top two intent scoring differential data 1014. In some embodiments, the top two intent scoring differential data 1014 may be generated by the contextual data management system 214. For example, the contextual data management system 214 may obtain scores for the top two intents in a manner similar to that described above, and then generate the top two intent scoring differential data 1014 by computing the difference between scores for the top two intents.

The device identification data 1016 may represent the identity of the voice-enabled device 102, the identity or presence of a feature of the voice-enabled device 102, or the like. For example, the device identification data 1016 may indicate whether the voice-enabled device 102 has a display screen. As another example, the device identification data 1016 may indicate a model of the voice-enabled device from which other properties or features of the device can be determined. In some embodiments, the device identification data 1016 may be generated by the contextual data management system 214. For example, an integration point may be triggered before or during processing by the ASR system 202, and the contextual data management system 214 may receive an identifier of the voice-enabled device 102. The contextual data management system 214 (or some other system or process initiated by the contextual data management system 214) may use that identifier as the device identification data 1016, or may use the identifier to look up or otherwise determine a feature of the voice-enabled device for device identification data 1016.

The example contextual signals shown in FIG. 10 and described herein are illustrative only, and are not intended to be limiting, required, or exhaustive. In some embodiments, the model 1000 may be trained to consider fewer, additional, and/or alternative contextual signals to generate routing evaluations for utterances with multi-domain triggers.

The model 1000 may analyze the contextual signals and generate a routing evaluation 1020, such as a score indicating a degree of confidence that the current domain is the proper domain for responding to the utterance. In some embodiments, the model may generate a classification instead of, or based on, a confidence score. For example, the confidence evaluation may be one of three classes indicating low, high, and moderate confidence, respectively.

In some embodiments, the model 1000 may be a machine learning model, such as artificial neural network trained using a corpus of training data to generate confidence evaluations. The model training may then be evaluated using a corpus of test data. In one specific, non-limiting embodiment, the model 1000 is a bi-directional long short-term memory (“Bi-LSTM”) model configured to receive a set of contextual data in an input vector and generate the routing evaluation 1020 based thereon.

When an utterance with a multi-domain trigger is received and a confidence request is sent to an intra-domain routing system 212, the system may use the model 1000 to obtain a confidence evaluation that the utterance is to be handled by the domain with which the intra-domain routing system 212 is associated. Otherwise, if the there is no multi-domain trigger, then intra-domain routing system 212 may proceed with routing evaluation methods such as those described above in which the intra-domain routing system 212 obtains routing confidence evaluations for various applications and/or subdomains.

FIG. 11 is a flow diagram of an illustrative process 1100 that may be performed to manage routing of utterances that include multi-domain triggers. Illustratively, the process 1100 may be performed by an intra-domain routing system 212. Portions of the process 1100 will be described with reference to the multi-domain, multi-tier hierarchy illustrated in FIG. 9 , and the example model 1000 shown in FIG. 10 . Additional portions of the process 1100 will be described with reference to FIGS. 12 and 13 , which are diagrams of illustrative data flows and interactions for routing evaluations of utterances with multi-domain triggers in various contexts.

The process 1100 begins at block 1102. When the process 1100 is initiated, a set of executable program instructions stored on one or more non-transitory computer-readable media (e.g., hard drive, flash memory, removable media, etc.) may be loaded into memory (e.g., random access memory or “RAM”) of a computing device and executed. For example, executable instructions may be loaded into memory 254 of a computing device of an intra-domain routing system 212 and executed by one or more processors 252. In some embodiments, the process 1100 or portions thereof may be implemented on multiple processors, serially or in parallel.

At block 1104, the intra-domain routing system 212 for a domain of applications associated with an intent, such as domain 206A with applications 282A-282D, may receive a confidence request regarding a particular intent. The confidence request may be generated by, or forwarded by, an inter-domain routing system 210 based on the association of the domain 206A with the intent. In the description that follows, this intent will be referred to as the current intent, and the domain for which the evaluation is being performed will be referred to as the current domain. For example, the intent may be a “shopping-search-item” intent for the shopping domain 206A.

At decision block 1106, the intra-domain routing system 212 may determine whether the intent that is the subject of the confidence request is a semantic representation of an utterance that includes a multi-domain trigger that is indicative of an utterance reasonably interpreted as being any number of different intents in any number of different domains, depending upon the context of the utterance. For example, a multi-domain trigger may be the word “show” at the beginning of an utterance, such as “Show security cameras.” If the utterance does not include any multi-domain trigger, the process 1100 can proceed to block 1108 where, in some embodiments, routing confidence evaluations may be generated as described in greater detail above. Otherwise, if the utterance does indeed include a multi-domain trigger, the process 1100 can proceed to block 1110.

FIG. 12 illustrates illustrative data flows and interactions between components of a speech processing system 100 to make routing determines for an utterance with a multi-domain trigger. As shown, the utterance 1200 in this example is “Show security cameras.” The utterance 1200 is processed by ASR system 202 and NLU system 204 into a set of candidate intents, including intent 1202A which is a “shopping-search-item” intent, and intent 1202B which is a “smart-home-display-video” intent.

The inter-domain routing system 210 identifies the shopping domain 206A as being associated with intent 1202A, and the smart home domain 206C as being associated with intent 1202B. The inter-domain routing system 210 sends confidence requests to the intra-domain routing systems 212A and 212C associated with domains 206A and 206C, respectively.

The intra-domain routing system 212A obtains a set of contextual data items 1204 for use in making a routing evaluation. As an initial matter, the intra-domain routing system 212 determines that the utterance 1200 includes a multi-domain trigger using, e.g., contextual data 1204, utterance data included in the confidence request, etc.

Returning to FIG. 11 , at block 1110 the intra-domain routing system 212A (or a routing confidence provider integrated with or associated with the intra-domain routing system 212A) can use a model or set of deterministic rules to evaluate a set of contextual data and generate a routing evaluation.

In some embodiments, as shown in FIG. 12 , the intra-domain routing system 212A may use a model 1000 to evaluate a set of contextual data items 1004 generated by or otherwise obtained by the contextual data management system 214. Output of the model 1000 may be a routing evaluation.

At decision block 1112, the intra-domain routing system 212A (or a routing confidence provider integrated with or associated with the intra-domain routing system 212A) can determine whether the routing evaluation indicates that the associated domain likely the proper domain to respond to the utterance. If the associated domain is not likely the proper domain to respond to the utterance, the process 1100 can proceed to block 1114 where output is generated indicating that the utterance is not to be assigned to the domain for responding. Otherwise, if the associated domain is likely the proper domain to respond to the utterance, the process 1100 can proceed to decision block 1116.

In some embodiments, the determination may be based on a criterion applied to the routing evaluation. For example, if the routing evaluation is a score, the determination may be based on whether the score satisfies a threshold or is within a range of scores indicative of the utterance being associated with the current domain. As another example, if the routing evaluation is a classification, the determination may be based on whether the classification is classification of the utterance being associated with the current domain.

In the example illustrated in FIG. 12 , the intra-domain routing system 212A may generate output 1206 specifying the associated domain 206 is not to handle the utterance based on the contextual data 1204, including contextual data indicating the user account associated with utterance has one or more security cameras already set up. The contextual data 1204 may additionally or alternatively represent other contextual signals, such as whether there are on-screen items currently displayed (e.g., when the utterance was made) that are associated with the smart home domain.

Returning to FIG. 11 , at decision block 1116 the intra-domain routing system 212A (or a routing confidence provider integrated with or associated with the intra-domain routing system 212A) can determine whether the intent for which the current routing evaluation is being made is to be up-ranked in the set of intent hypotheses generated from the utterance. The determination may be made based on a position of the current intent within the set of hypotheses (e.g., whether the current intent is the top-ranked intent, second-to-top-ranked intent, or lower), the routing evaluation (e.g., the confidence score), other data, or some combination thereof. If the routing evaluation for the current intent indicates a relatively high confidence that the current domain is to respond to the utterance (e.g., the routing evaluation is a score satisfying a threshold) and the intent is not the top-ranked intent in the N-best list, then the intra-domain routing system 212A may determine that the intent is to be up-ranked.

If the intent is to be up-ranked, the process may proceed to block 1118 where output is generated indicating the current intent and assignment to the current domain is to be up-ranked. Otherwise, if the intent is not to be up-ranked, the process may proceed to block 1120 where output is generated indicated the routing evaluation output. The process 1100 may end at block 1122.

In some embodiments, the output may be an enumerated type or other value from a set of possible values indicting a degree of confidence in assignment of the current intent to the current domain. For example, the output may be one of “yes,” “maybe,” or “do_not_assign.” An output of “yes” for an intent that is not the top-ranked intent in the N-best list may serve as a signal that the intent and corresponding assignment to the current domain are to be up-ranked. An output of “do_not_assign” for the current intent may serve as a signal that the current domain is not to be assigned to handle the utterance, even if the current intent is the top-ranked intent in the N-best list.

FIG. 13 illustrates an example in which the routing evaluation output 1306 indicates that the utterance is likely to be associated with the current domain and, if the current intent is not the top-ranked intent, the current intent is to be up-ranked. As shown, the user 104 makes the utterance 1300 “Show coconut rice.” Content is shown on screen related to the shopping domain 206A, such as results of a search to purchase Spanish rice. The intent 1302A that the intra-domain routing system 212A is evaluating is a “shopping-search-item” intent, while a separate intra-domain routing system 212B for the recipe domain 206A is evaluating a “recipe-get-ingredient” intent 1302B. Illustratively, intent 1302B may be ranked higher initially than intent 1302A.

The intra-domain routing system 212A obtains contextual data 1304, including contextual data indicating that shopping search results were displayed on screen when the utterance 1300 was made. The intra-domain routing system 212A evaluates this set of contextual data 1304 using a model 1000 and generates output 1306 output indicating a high degree of confidence that the utterance is to be processed by the shopping domain 206A. In this example, the intent 1302A associated with the shopping domain 206A can be up-ranked over the intent 1302B from the recipe domain 206B so that the shopping domain 206A handles responding to the utterance 1300.

Terminology

Depending on the embodiment, certain acts, events, or functions of any of the processes or algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described operations or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, operations or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.

The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or combinations of electronic hardware and computer software. To clearly illustrate this interchangeability, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, or as software that runs on hardware, depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.

Moreover, the various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor device, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A processor device can be a microprocessor, but in the alternative, the processor device can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor device can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor device includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor device can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor device may also include primarily analog components. For example, some or all of the algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.

The elements of a method, process, routine, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor device, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor device such that the processor device can read data from, and write data to, the storage medium. In the alternative, the storage medium can be integral to the processor device. The processor device and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor device and the storage medium can reside as discrete components in a user terminal.

Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without other input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.

Unless otherwise explicitly stated, articles such as “a” or “an” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.

While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As can be recognized, certain embodiments described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain embodiments disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. 

What is claimed is:
 1. A system comprising: computer-readable memory storing executable instructions; and one or more processors in communication with the computer-readable memory and configured by the executable instructions to at least: receive audio data from a voice-enabled device, wherein the audio data represents an utterance comprising a multi-domain trigger word or phrase; generate intent data comprising a plurality of semantic representations of the utterance; identify a first domain of an intent processing application hierarchy based at least partly on an association of the first domain with a semantic representation of the plurality of semantic representations, wherein the intent processing application hierarchy comprises a plurality of domains, and wherein the first domain comprises a plurality of applications configured to generate responses to utterances associated with the semantic representation; determine that the utterance comprises the multi-domain trigger word or phrase; analyze a plurality of contextual signals associated with the utterance using a statistical model, wherein the plurality of contextual signals comprises a first contextual signal representing one or more items presented on a display when the utterance was made, and wherein a second contextual signal of the plurality of contextual signals indicates whether the semantic representation is a top-ranked semantic representation of the plurality of semantic representations; determine, based on results of analyzing the plurality of contextual signals, that an application of the first domain is to generate a response; and generate the response using the application.
 2. The system of claim 1, wherein the one or more processors are configured by further executable instructions to up-rank the semantic representation with respect to a second semantic representation of the plurality of semantic representations, wherein the semantic representation is initially ranked below the second semantic representation in the plurality of semantic representations.
 3. The system of claim 1, wherein the plurality of contextual signals comprises at least one of: domain negative gazetteer data; domain on-screen item similarity score data; extra-domain on-screen item similarity score data; top-scoring intent identification data; second-scoring intent identification data; top two intent scoring differential data; or device identification data.
 4. The system of claim 1, wherein the one or more processors are configured by further executable instructions to train the statistical model using training data representing a plurality of utterances, wherein each of the utterances includes the multi-domain trigger word or phrase, and wherein each of the utterances is associated with a respective set of contextual signals.
 5. A computer-implemented method comprising: as performed by one or more computer processors configured to execute specific instructions, receiving, by an inter-domain routing system, a plurality of semantic representations of an utterance comprising a multi-domain trigger; generating, by the inter-domain routing system: a first request for a first routing evaluation associated with a first domain of a plurality of domains, wherein the first domain is associated with a first semantic representation; and a second request for a second routing evaluation associated with a second domain of the plurality of domains, wherein the second domain is associated with a second semantic representation; and in response to the first request, generating, by an intra-domain routing system associated with the first domain, routing evaluation data indicating whether an application of the first domain is to generate a response to the utterance, the routing evaluation data generated using: a model associated with the multi-domain trigger, and contextual data associated with the second domain.
 6. The computer-implemented method of claim 5, further comprising obtaining, by the intra-domain routing system, the contextual data, wherein the contextual data comprises at least one of: domain negative gazetteer data; domain on-screen item similarity score data; extra-domain on-screen item similarity score data; top-scoring intent identification data; second-scoring intent identification data; top two intent scoring differential data; or device identification data.
 7. The computer-implemented method of claim 5, further comprising determining, by the intra-domain routing system, to up-rank the first semantic representation with respect to the second semantic representation, wherein the first semantic representation is ranked below the second semantic representation in the plurality of semantic representations received by the inter-domain routing system.
 8. The computer-implemented method of claim 5, further comprising determining, by the intra-domain routing system, that the first application is not to generate the response, wherein the routing evaluation data indicates that the first application is not to generate the response.
 9. The computer-implemented method of claim 5, wherein generating the routing evaluation data using the model and the contextual data comprises generating a score using a statistical model configured to receive the contextual data as input, wherein the score represents a degree of confidence that the application is to generate the response.
 10. The computer-implemented method of claim 5, further comprising determining, by the intra-domain routing system, that the utterance comprises the multi-domain trigger, wherein the routing evaluation data is generated in response to determining that the utterance comprises the multi-domain trigger.
 11. The computer-implemented method of claim 5, further comprising: executing a set of natural language processing actions on natural language input to generate the plurality of semantic representations, wherein the natural language input represents the utterance; determining, at an integration point during the set of natural language processing actions, to generate a first contextual data item using an initial data item associated with at least one of the set of natural language processing actions; and generating the first contextual data item based at least partly on the initial data item concurrently with performance of at least a portion of the set of natural language processing actions.
 12. The computer-implemented method of claim 5, further comprising training the model using training data representing a plurality of utterances, wherein each of the utterances includes the multi-domain trigger, and wherein each of the utterances is associated with a respective set of contextual data.
 13. A computer-implemented method comprising: as performed by one or more computer processors configured to execute specific instructions, receiving, by an inter-domain routing system, a plurality of semantic representations of an utterance comprising a multi-domain trigger; generating, by the inter-domain routing system: a first request for a first routing evaluation associated with a first domain of a plurality of domains, wherein the first domain comprises a first application configured to generate content presentation responses associated with a first semantic representation; and a second request for a second routing evaluation associated with a second domain of the plurality of domains, wherein the second domain comprises a second application configured to generate content presentation responses associated with a second semantic representation; and in response to the first request, generating, by an intra-domain routing system associated with the first domain, routing evaluation data indicating whether the first application is to generate a response to the utterance, the routing evaluation data generated using: a model associated with the multi-domain trigger, and contextual data associated with the utterance.
 14. The computer-implemented method of claim 13, further comprising obtaining, by the intra-domain routing system, the contextual data, wherein the contextual data comprises at least one of: domain negative gazetteer data; domain on-screen item similarity score data; extra-domain on-screen item similarity score data; top-scoring intent identification data; second-scoring intent identification data; top two intent scoring differential data; or device identification data.
 15. The computer-implemented method of claim 13, further comprising determining, by the intra-domain routing system, to up-rank the first semantic representation with respect to the second semantic representation, wherein the first semantic representation is ranked below the second semantic representation in the plurality of semantic representations received by the inter-domain routing system.
 16. The computer-implemented method of claim 13, further comprising determining, by the intra-domain routing system, that the first application is not to generate the response, wherein the routing evaluation data indicates that the first application is not to generate the response.
 17. The computer-implemented method of claim 13, wherein generating the routing evaluation data using the model and the set of contextual data items comprises generating a score using a statistical model configured to receive the contextual data as input, wherein the score represents a degree of confidence that the first application is to generate the response.
 18. The computer-implemented method of claim 13, further comprising determining, by the intra-domain routing system, that the utterance comprises the multi-domain trigger, wherein the routing evaluation data is generated in response to determining that the utterance comprises the multi-domain trigger.
 19. The computer-implemented method of claim 13, further comprising training the model using training representing a plurality of utterances, wherein each of the utterances includes the multi-domain trigger, and wherein each of the utterances is associated with a respective set of contextual data.
 20. The computer-implemented method of claim 13, further comprising generating, by the first application, the response as a content presentation response comprising display instructions to display at least one of: a search result, item information, or content from a smart home device. 